Devices and methods for power allocation

ABSTRACT

Methods and devices for allocating power among a plurality of circuits in a communication device, including determining a power budget for allocating to the plurality of circuits from a power supply information; receiving an activity status from a first circuit of the plurality of circuits; determining a first power value based on the activity status; deriving a second power value based on the first power value and the power budget; and allocating power to one or more remaining circuits of the plurality of circuits based on the second power value.

TECHNICAL FIELD

Various aspects relate generally to power allocation for devicesconfigured for wireless communications.

BACKGROUND

Terminal device peak power (Pmax) requirements have been growing fromgeneration to generation, driven by a continuing trend of increasedcompute requirements, for example graphics, core count, and input/output(I/O) capabilities, e.g. memory bandwidth and timing parameters. At thesame time, power delivery capabilities have not increased to account forthese increased compute requirements, thereby effectively limiting orreducing the amount of peak power available to a terminal device's othercomponents, e.g. a device's Application Processor (AP, or System on Chip(SoC)).

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference characters generally refer to the sameparts throughout the different views. The drawings are not necessarilyto scale, emphasis instead generally being placed upon illustrating theprinciples of the invention. In the following description, variousembodiments of the invention are described with reference to thefollowing drawings, in which:

FIG. 1 shows an exemplary radio communication network according to someaspects;

FIG. 2 shows an internal configuration of terminal device according tosome aspects;

FIG. 3 shows an exemplary configuration of signal acquisition andprocessing circuitry according to some aspects;

FIG. 4 shows an exemplary configuration of a network access nodeinterfacing with core network according to some aspects;

FIG. 5 shows a graph illustrating the power margin between Pmax limitand platform operating power in current systems employing the worst caseapproach to protect against Pmax events according to some aspects;

FIG. 6 shows a schematic diagram of a platform peak power manager (PPM)according to some aspects;

FIG. 7 shows a schematic diagram of a baseband modem with a modem Pmaxestimator according to some aspects;

FIG. 8 shows a second schematic diagram of a baseband modem with a modemPmax estimator according to some aspects;

FIGS. 9 and 10 show exemplary graphs for typical LTE modem Pmaxconsumption according to some aspects;

FIG. 11 shows a diagram illustrating a mapping of modem operation tomodem Pmax demand according to some aspects;

FIG. 12 shows an exemplary graph of a modem event timing and Pmax levelsfor a mobile terminated (MT) LTE data according to some aspects;

FIG. 13 shows graphs illustrating worst case Pmax events according tosome aspects;

FIG. 14 shows a schematic diagram of a baseband modem with a Modem PmaxEstimator and a Thermal Manager according to some aspects;

FIG. 15 shows a graph showing modem temperature and throttle stateindications according to some aspects;

FIG. 16 shows a schematic diagram of an internal configuration ofcontroller according to some aspects;

FIG. 17 shows a flowchart according to some aspects;

FIG. 18 shows system implementing a rigid architecture;

FIGS. 19 and 20 show graphs illustrating parameters for a BatteryDischarge Controller (BDC) to account for in some aspects

FIG. 21 shows a graph illustrating features that a battery dischargecontroller (BDC) may implement to determine discharge capacity for acommunication device in some aspects;

FIG. 22 shows a schematic diagram of a Network on Chip (NoC) with aBattery Discharge Controller (BDC) according to some aspects;

FIGS. 23 and 24 show two exemplary configurations of a plurality ofprocessing cores according to some aspects;

FIG. 25 shows a flowchart for a method for battery discharge controlaccording to some aspects;

FIG. 26 shows a supplementary flowchart for a method for batterydischarge control according to some aspects; and

FIG. 27 shows a schematic diagram of an internal configuration ofcontroller according to some aspects.

DESCRIPTION

The following detailed description refers to the accompanying drawingsthat show, by way of illustration, specific details and embodiments inwhich the invention may be practiced.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration”. Any embodiment or design described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments or designs.

The words “plurality” and “multiple” in the description or the claimsexpressly refer to a quantity greater than one. The terms “group (of)”,“set [of]”, “collection (of)”, “series (of)”, “sequence (of)”, “grouping(of)”, etc., and the like in the description or in the claims refer to aquantity equal to or greater than one, i.e. one or more. Any termexpressed in plural form that does not expressly state “plurality” or“multiple” likewise refers to a quantity equal to or greater than one.The terms “proper subset”, “reduced subset”, and “lesser subset” referto a subset of a set that is not equal to the set, i.e. a subset of aset that contains less elements than the set.

It is appreciated that any vector and/or matrix notation utilized hereinis exemplary in nature and is employed solely for purposes ofexplanation. Accordingly, it is understood that the approaches detailedin this disclosure are not limited to being implemented solely usingvectors and/or matrices, and that the associated processes andcomputations may be equivalently performed with respect to sets,sequences, groups, etc., of data, observations, information, signals,samples, symbols, elements, etc. Furthermore, it is appreciated thatreferences to a “vector” may refer to a vector of any size ororientation, e.g. including a 1×1 vector (e.g. a scalar), a 1×M vector(e.g. a row vector), and an M×1 vector (e.g. a column vector).Similarly, it is appreciated that references to a “matrix” may refer tomatrix of any size or orientation, e.g. including a 1×1 matrix (e.g. ascalar), a 1×M matrix (e.g. a row vector), and an M×1 matrix (e.g. acolumn vector).

The terms “circuit” or “circuitry” as used herein are understood as anykind of logic-implementing entity, which may include special-purposehardware or a processor executing software. A circuit may thus be ananalog circuit, digital circuit, mixed-signal circuit, logic circuit,processor, microprocessor, Central Processing Unit (CPU), GraphicsProcessing Unit (GPU), Digital Signal Processor (DSP), FieldProgrammable Gate Array (FPGA), integrated circuit, Application SpecificIntegrated Circuit (ASIC), etc., or any combination thereof. Any otherkind of implementation of the respective functions which will bedescribed below in further detail may also be understood as a “circuit”.It is understood that any two (or more) of the circuits detailed hereinmay be realized as a single circuit with substantially equivalentfunctionality, and conversely that any single circuit detailed hereinmay be realized as two (or more) separate circuits with substantiallyequivalent functionality. Additionally, references to a “circuit” mayrefer to two or more circuits that collectively form a single circuit.The term “circuit arrangement” may refer to a single circuit, acollection of circuits, and/or an electronic device composed of one ormore circuits.

As used herein, “memory” may be understood as a non-transitorycomputer-readable medium in which data or information can be stored forretrieval. References to “memory” included herein may thus be understoodas referring to volatile or non-volatile memory, including random accessmemory (RAM), read-only memory (ROM), flash memory, solid-state storage,magnetic tape, hard disk drive, optical drive, etc., or any combinationthereof. Furthermore, it is appreciated that registers, shift registers,processor registers, data buffers, etc., are also embraced herein by theterm memory. It is appreciated that a single component referred to as“memory” or “a memory” may be composed of more than one different typeof memory, and thus may refer to a collective component comprising oneor more types of memory. It is readily understood that any single memorycomponent may be separated into multiple collectively equivalent memorycomponents, and vice versa. Furthermore, while memory may be depicted asseparate from one or more other components (such as in the drawings), itis understood that memory may be integrated within another component,such as on a common integrated chip.

The term “software” refers to any type of executable instruction,including firmware.

The term “terminal device” utilized herein refers to user-side devices(both mobile and immobile) that can connect to a core network andvarious external networks via a radio access network. “Terminal device”can include any mobile or immobile wireless communication device,including User Equipments (UEs), Mobile Stations (MSs), Stations (STAs),cellular phones, tablets, laptops, personal computers, wearables,multimedia playback and other handheld electronic devices,consumer/home/office/commercial appliances, vehicles, and any otherelectronic device capable of user-side wireless communications. Withoutloss of generality, in some cases terminal devices can also includeapplication-layer components, such as application processors or othergeneral processing components, that are directed to functionality otherthan wireless communications. Terminal devices can also support wiredcommunications in addition to wireless communications. Furthermore,terminal devices can include vehicular communication devices thatfunction as terminal devices.

The term “network access node” as utilized herein refers to anetwork-side device that provides a radio access network with whichterminal devices can connect and exchange information with othernetworks through the network access node. “Network access nodes” caninclude any type of base station or access point, including macro basestations, micro base stations, NodeBs, evolved NodeBs (eNodeBs or eNBs),Home eNodeBs, Remote Radio Heads (RRHs), relay points, Wi-Fi/WLAN AccessPoints (APs), Bluetooth master devices, DSRC RSUs, terminal devicesacting as network access nodes, and any other electronic device capableof network-side wireless communications, including both immobile andmobile devices (e.g., vehicular network access nodes, mobile cells, andother movable network access nodes). As used herein, a “cell” in thecontext of telecommunications may be understood as a sector served by anetwork access node. Accordingly, a cell may be a set of geographicallyco-located antennas that correspond to a particular sectorization of anetwork access node. A network access node can thus serve one or morecells (or sectors), where each cell is characterized by a distinctcommunication channel. Furthermore, the term “cell” may be utilized torefer to any of a macrocell, microcell, femtocell, picocell, etc.Certain communication devices can act as both terminal devices andnetwork access nodes, such as a terminal device that provides a networkconnection for other terminal devices.

The term “base station” used in reference to an access point of a mobilecommunication network may be understood as a macro base station, microbase station, Node B, evolved NodeB (eNB), Home eNodeB, Remote RadioHead (RRH), relay point, etc. As used herein, a “cell” in the context oftelecommunications may be understood as a sector served by a basestation. Accordingly, a cell may be a set of geographically co-locatedantennas that correspond to a particular sectorization of a basestation. A base station may thus serve one or more cells (or sectors),where each cell is characterized by a distinct communication channel.Furthermore, the term “cell” may be utilized to refer to any of amacrocell, microcell, femtocell, picocell, etc.

Various aspects of this disclosure may utilize or be related to radiocommunication technologies. While some examples may refer to specificradio communication technologies, these examples are demonstrative andmay be analogously applied to other radio communication technologies,including, but not limited to, a Global System for Mobile Communications(GSM) radio communication technology, a General Packet Radio Service(GPRS) radio communication technology, an Enhanced Data Rates for GSMEvolution (EDGE) radio communication technology, and/or a ThirdGeneration Partnership Project (3GPP) radio communication technology,for example Universal Mobile Telecommunications System (UMTS), Freedomof Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP LongTerm Evolution Advanced (LTE Advanced), Code division multiple access2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, ThirdGeneration (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDMA (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-SCDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd GenerationPartnership Project Release 9), 3GPP Rel. 10 (3rd Generation PartnershipProject Release 10) 3GPP Rel. 11 (3rd Generation Partnership ProjectRelease 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPPRel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15(3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rdGeneration Partnership Project Release 16), 3GPP Rel. 17 (3rd GenerationPartnership Project Release 17), 3GPP Rel. 18 (3rd GenerationPartnership Project Release 18), 3GPP 5G, 3GPP LTE Extra, LTE-AdvancedPro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS TerrestrialRadio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA),Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)),cdmaOne (2G), Code division multiple access 2000 (Third generation)(CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only(EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)),Total Access Communication System/Extended Total Access CommunicationSystem (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)),Push-to-talk (PTT), Mobile Telephone System (MTS), Improved MobileTelephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT(Norwegian for Offentlig Landmobil Telefoni, Public Land MobileTelephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, orMobile telephony system D), Public Automated Land Mobile (Autotel/PALM),ARP (Finnish for Autoradiopuhelin, “car radio phone”), NMT (NordicMobile Telephony), High capacity version of NTT (Nippon Telegraph andTelephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex,DataTAC, Integrated Digital Enhanced Network (iDEN), Personal DigitalCellular (PDC), Circuit Switched Data (CSD), Personal Handy-phone System(PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst,Unlicensed Mobile Access (UMA), also referred to as 3GPP Generic AccessNetwork, or GAN standard), Zigbee, Bluetooth®, Wireless Gigabit Alliance(WiGig) standard, mmWave standards in general (wireless systemsoperating at 10-300 GHz and above such as WiGig, IEEE 802.1 lad, IEEE802.1 lay, etc.), technologies operating above 300 GHz and THz bands,(3GPP/LTE based or IEEE 802.11p and other) Vehicle-to-Vehicle (V2V) andVehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) andInfrastructure-to-Vehicle (I2V) communication technologies, 3GPPcellular V2X, DSRC (Dedicated Short Range Communications) communicationsystems such as Intelligent-Transport-Systems, and other existing,developing, or future radio communication technologies. Aspectsdescribed herein may use such radio communication technologies accordingto various spectrum management schemes, including, but not limited to,dedicated licensed spectrum, unlicensed spectrum, (licensed) sharedspectrum (such as LSA=Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6GHz, 3.6-3.8 GHz and further frequencies and SAS=Spectrum Access Systemin 3.55-3.7 GHz and further frequencies), and may be use variousspectrum bands including, but not limited to, IMT (International MobileTelecommunications) spectrum (including 450-470 MHz, 790-960 MHz,1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2500-2690 MHz, 698-790 MHz,610-790 MHz, 3400-3600 MHz, etc., where some bands may be limited tospecific region(s) and/or countries), IMT-advanced spectrum, IMT-2020spectrum (expected to include 3600-3800 MHz, 3.5 GHz bands, 700 MHzbands, bands within the 24.25-86 GHz range, etc.), spectrum madeavailable under FCC's “Spectrum Frontier” 5G initiative (including27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz,42-42.5 GHz, 57-64 GHz, 64-71 GHz, 71-76 GHz, 81-86 GHz and 92-94 GHz,etc.), the ITS (Intelligent Transport Systems) band of 5.9 GHz(typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated toWiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88GHz), the 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71 GHz,bands currently allocated to automotive radar applications such as 76-81GHz, and future bands including 94-300 GHz and above. Furthermore,aspects described herein can also employ radio communicationtechnologies on a secondary basis on bands such as the TV White Spacebands (typically below 790 MHz) where in particular the 400 MHz and 700MHz bands are prospective candidates. Besides cellular applications,specific applications for vertical markets may be addressed such as PMSE(Program Making and Special Events), medical, health, surgery,automotive, low-latency, drones, etc. applications. Furthermore, aspectsdescribed herein may also use radio communication technologies with ahierarchical application, such as by introducing a hierarchicalprioritization of usage for different types of users (e.g.,low/medium/high priority, etc.), based on a prioritized access to thespectrum e.g. with highest priority to tier-1 users, followed by tier-2,then tier-3, etc. users, etc. Aspects described herein can also useradio communication technologies with different Single Carrier or OFDMflavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier(FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio), which caninclude allocating the OFDM carrier data bit vectors to thecorresponding symbol resources.

For purposes of this disclosure, radio communication technologies may beclassified as one of a Short Range radio communication technology orCellular Wide Area radio communication technology. Short Range radiocommunication technologies include Bluetooth, WLAN (e.g. according toany IEEE 802.11 standard), and other similar radio communicationtechnologies. Cellular Wide Area radio communication technologiesinclude Global System for Mobile Communications (GSM), Code DivisionMultiple Access 2000 (CDMA2000), Universal Mobile TelecommunicationsSystem (UMTS), Long Term Evolution (LTE), General Packet Radio Service(GPRS), Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSMEvolution (EDGE), High Speed Packet Access (HSPA; including High SpeedDownlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA),HSDPA Plus (HSDPA+), and HSUPA Plus (HSUPA+)), WorldwideInteroperability for Microwave Access (WiMax) (e.g. according to an IEEE802.16 radio communication standard, e.g. WiMax fixed or WiMax mobile),etc., and other similar radio communication technologies. Cellular WideArea radio communication technologies also include “small cells” of suchtechnologies, such as microcells, femtocells, and picocells. CellularWide Area radio communication technologies may be generally referred toherein as “cellular” communication technologies. It is understood thatexemplary scenarios detailed herein are demonstrative in nature, andaccordingly may be similarly applied to various other mobilecommunication technologies, both existing and not yet formulated,particularly in cases where such mobile communication technologies sharesimilar features as disclosed regarding the following examples.Furthermore, as used herein the term GSM refers to both circuit- andpacket-switched GSM, including, for example, GPRS, EDGE, and any otherrelated GSM technologies. Likewise, the term UMTS refers to bothcircuit- and packet-switched UMTS, including, for example, HSPA,HSDPA/HSUPA, HSDPA+/HSUPA+, and any other related UMTS technologies. Asused herein, a first radio communication technology is different from asecond radio communication technology if the first and second radiocommunication technologies are based on different communicationstandards.

The term “network” as utilized herein, e.g. in reference to acommunication network such as a radio communication network, encompassesboth an access section of a network (e.g. a radio access network (RAN)section) and a core section of a network (e.g. a core network section).The term “radio idle mode” or “radio idle state” used herein inreference to a terminal device refers to a radio control state in whichthe terminal device is not allocated at least one dedicatedcommunication channel of a mobile communication network. The term “radioconnected mode” or “radio connected state” used in reference to aterminal device refers to a radio control state in which the terminaldevice is allocated at least one dedicated uplink communication channelof a radio communication network.

Unless explicitly specified, the term “transmit” encompasses both direct(point-to-point) and indirect transmission (via one or more intermediarypoints). Similarly, the term “receive” encompasses both direct andindirect reception. Furthermore, the terms “transmit”, “receive”,“communicate”, and other similar terms encompass both physicaltransmission (e.g., the transmission of radio signals) and logicaltransmission (e.g., the transmission of digital data over a logicalsoftware-level connection). For example, a processor may transmit orreceive data in the form of radio signals with another processor, wherethe physical transmission and reception is handled by radio-layercomponents such as RF transceivers and antennas, and the logicaltransmission and reception is performed by the processor. The term“communicate” encompasses one or both of transmitting and receiving,i.e. unidirectional or bidirectional communication in one or both of theincoming and outgoing directions. The term “calculate” encompass both‘direct’ calculations via a mathematical expression/formula/relationshipand ‘indirect’ calculations via lookup or hash tables and other arrayindexing or searching operations.

FIG. 1 shows exemplary radio communication network 100 according to someaspects, which may include terminal devices 102 and 104, access nodes(i.e. network access points) 110 and 120 with corresponding coverageregions (i.e. cells) 111 and 121, respectively. Communication network100 may communicate via network access nodes 110 and 120 with terminaldevices 102 and 104 via various mechanisms. Although certain examplesdescribed herein may refer to a particular radio access network context(e.g., LTE, UMTS, GSM, other 3rd Generation Partnership Project (3GPP)networks, WLAN/WiFi, Bluetooth, 5G, mmWave, etc.), these examples aredemonstrative and may therefore be analogously applied to any other typeor configuration of radio access network. The number of network accessnodes and terminal devices in radio communication network 100 isexemplary and is scalable to any amount.

In an exemplary cellular context, network access nodes 110 and 120 maybe base stations (e.g., eNodeBs, NodeBs, Base Transceiver Stations(BTSs), or any other type of base station), while terminal devices 102and 104 may be cellular terminal devices (e.g., Mobile Stations (MSs),User Equipments (UEs), or any type of cellular terminal device). Networkaccess nodes 110 and 120 may therefore interface (e.g., via backhaulinterfaces) with a cellular core network such as an Evolved Packet Core(EPC, for LTE), Core Network (CN, for UMTS), or other cellular corenetworks, which may also be considered part of radio communicationnetwork 100. The cellular core network may interface with one or moreexternal data networks. In an exemplary short-range context, networkaccess node 110 and 120 may be access points (APs, e.g., WLAN or WiFiAPs), while terminal device 102 and 104 may be short range terminaldevices (e.g., stations (STAs)). Network access nodes 110 and 120 mayinterface (e.g., via an internal or external router) with one or moreexternal data networks.

Network access nodes 110 and 120 (and, optionally, other network accessnodes of radio communication network 100 not explicitly shown in FIG. 1)may accordingly provide a radio access network to terminal devices 102and 104 (and, optionally, other terminal devices of radio communicationnetwork 100 not explicitly shown in FIG. 1). In an exemplary cellularcontext, the radio access network provided by network access nodes 110and 120 may enable terminal devices 102 and 104 to wirelessly access thecore network via radio communications. The core network may provideswitching, routing, and transmission, for traffic data related toterminal devices 102 and 104, and may further provide access to variousinternal data networks (e.g., control nodes, routing nodes that transferinformation between other terminal devices on radio communicationnetwork 100, etc.) and external data networks (e.g., data networksproviding voice, text, multimedia (audio, video, image), and otherInternet and application data). In an exemplary short-range context, theradio access network provided by network access nodes 110 and 120 mayprovide access to internal data networks (e.g., for transferring databetween terminal devices connected to radio communication network 100)and external data networks (e.g., data networks providing voice, text,multimedia (audio, video, image), and other Internet and applicationdata).

The radio access network and core network (if applicable, e.g. for acellular context) of radio communication network 100 may be governed bycommunication protocols that can vary depending on the specifics ofradio communication network 100. Such communication protocols may definethe scheduling, formatting, and routing of both user and control datatraffic through radio communication network 100, which includes thetransmission and reception of such data through both the radio accessand core network domains of radio communication network 100.Accordingly, terminal devices 102 and 104 and network access nodes 110and 120 may follow the defined communication protocols to transmit andreceive data over the radio access network domain of radio communicationnetwork 100, while the core network may follow the defined communicationprotocols to route data within and outside of the core network.Exemplary communication protocols include LTE, UMTS, GSM, WiMAX,Bluetooth, WiFi, mmWave, etc., any of which may be applicable to radiocommunication network 100.

FIG. 2 shows an internal configuration of terminal device 102 accordingto some aspects, which may include antenna system 202, radio frequency(RF) transceiver 204, baseband modem 206 (including digital signalprocessor 208 and controller 210), application processor 212, memory214, and power supply 216. Although not explicitly shown in FIG. 2, insome aspects terminal device 102 may include one or more additionalhardware and/or software components, such as processors/microprocessors,controllers/microcontrollers, other specialty or generichardware/processors/circuits, peripheral device(s), memory, powersupply, external device interface(s), subscriber identity module(s)(SIMs), user input/output devices (display(s), keypad(s),touchscreen(s), speaker(s), external button(s), camera(s),microphone(s), etc.), or other related components.

Terminal device 102 may transmit and receive radio signals on one ormore radio access networks. Baseband modem 206 may direct suchcommunication functionality of terminal device 102 according to thecommunication protocols associated with each radio access network, andmay execute control over antenna system 202 and RF transceiver 204 inorder to transmit and receive radio signals according to the formattingand scheduling parameters defined by each communication protocol.Although various practical designs may include separate communicationcomponents for each supported radio communication technology (e.g., aseparate antenna, RF transceiver, digital signal processor, andcontroller), for purposes of conciseness the configuration of terminaldevice 102 shown in FIG. 2 depicts only a single instance of suchcomponents.

Terminal device 102 may transmit and receive wireless signals withantenna system 202, which may be a single antenna or an antenna arraythat includes multiple antennas. In some aspects, antenna system 202 mayadditionally include analog antenna combination and/or beamformingcircuitry. In the receive (RX) path, RF transceiver 204 may receiveanalog radio frequency signals from antenna system 202 and performanalog and digital RF front-end processing on the analog radio frequencysignals to produce digital baseband samples (e.g., In-Phase/Quadrature(IQ) samples) to provide to baseband modem 206. RF transceiver 204 mayinclude analog and digital reception components including amplifiers(e.g., Low Noise Amplifiers (LNAs)), filters, RF demodulators (e.g., RFIQ demodulators)), and analog-to-digital converters (ADCs), which RFtransceiver 204 may utilize to convert the received radio frequencysignals to digital baseband samples. In the transmit (TX) path, RFtransceiver 204 may receive digital baseband samples from baseband modem206 and perform analog and digital RF front-end processing on thedigital baseband samples to produce analog radio frequency signals toprovide to antenna system 202 for wireless transmission. RF transceiver204 may thus include analog and digital transmission componentsincluding amplifiers (e.g., Power Amplifiers (PAs), filters, RFmodulators (e.g., RF IQ modulators), and digital-to-analog converters(DACs), which RF transceiver 204 may utilize to mix the digital basebandsamples received from baseband modem 206 and produce the analog radiofrequency signals for wireless transmission by antenna system 202. Insome aspects baseband modem 206 may control the RF transmission andreception of RF transceiver 204, including specifying the transmit andreceive radio frequencies for operation of RF transceiver 204.

As shown in FIG. 2, baseband modem 206 may include digital signalprocessor 208, which may perform physical layer (PHY, Layer 1)transmission and reception processing to, in the transmit path, prepareoutgoing transmit data provided by controller 210 for transmission viaRF transceiver 204, and, in the receive path, prepare incoming receiveddata provided by RF transceiver 204 for processing by controller 210.Digital signal processor 208 may be configured to perform one or more oferror detection, forward error correction encoding/decoding, channelcoding and interleaving, channel modulation/demodulation, physicalchannel mapping, radio measurement and search, frequency and timesynchronization, antenna diversity processing, power control andweighting, rate matching/de-matching, retransmission processing,interference cancellation, and any other physical layer processingfunctions. Digital signal processor 208 may be structurally realized ashardware components (e.g., as one or more digitally-configured hardwarecircuits or FPGAs), software-defined components (e.g., one or moreprocessors configured to execute program code defining arithmetic,control, and I/O instructions (e.g., software and/or firmware) stored ina non-transitory computer-readable storage medium, which may includedata stored in on-chip memory such as SRAM, register files, or externalDRAM), or as a combination of hardware and software components. In someaspects, digital signal processor 208 may include one or more processorsconfigured to retrieve and execute program code that defines control andprocessing logic for physical layer processing operations. In someaspects, digital signal processor 208 may execute processing functionswith software via the execution of executable instructions. In someaspects, digital signal processor 208 may include one or more dedicatedhardware circuits (e.g., ASICs, FPGAs, and other hardware) that aredigitally configured to specific execute processing functions, where theone or more processors of digital signal processor 208 may offloadcertain processing tasks to these dedicated hardware circuits, which areknown as hardware accelerators. Exemplary hardware accelerators caninclude Fast Fourier Transform (FFT) circuits and encoder/decodercircuits. In some aspects, the processor and hardware acceleratorcomponents of digital signal processor 208 may be realized as a coupledintegrated circuit.

Terminal device 102 may be configured to operate according to one ormore radio communication technologies. Digital signal processor 208 maybe responsible for lower-layer processing functions of the radiocommunication technologies, while controller 210 may be responsible forupper-layer protocol stack functions. Controller 210 may thus beresponsible for controlling the radio communication components ofterminal device 102 (antenna system 202, RF transceiver 204, and digitalsignal processor 208) in accordance with the communication protocols ofeach supported radio communication technology, and accordingly mayrepresent the Access Stratum and Non-Access Stratum (NAS) (alsoencompassing Layer 2 and Layer 3) of each supported radio communicationtechnology. Controller 210 may be structurally embodied as a protocolprocessor configured to execute protocol software (retrieved from acontroller memory) and subsequently control the radio communicationcomponents of terminal device 102 in order to transmit and receivecommunication signals in accordance with the corresponding protocolcontrol logic defined in the protocol software. Controller 210 mayinclude one or more processors configured to retrieve and executeprogram code that defines the upper-layer protocol stack logic for oneor more radio communication technologies, which can include Data LinkLayer/Layer 2 and Network Layer/Layer 3 functions. Controller 210 may beconfigured to perform both user-plane and control-plane functions tofacilitate the transfer of application layer data to and from radioterminal device 102 according to the specific protocols of the supportedradio communication technology. User-plane functions can include headercompression and encapsulation, security, error checking and correction,channel multiplexing, scheduling and priority, while control-planefunctions may include setup and maintenance of radio bearers. Theprogram code retrieved and executed by controller 210 may includeexecutable instructions that define the logic of such functions.

Accordingly, baseband modem 206 may be configured to implement themethods and/or algorithms described in this disclosure.

In some aspects, terminal device 102 may be configured to transmit andreceive data according to multiple radio communication technologies.Accordingly, in some aspects one or more of antenna system 202, RFtransceiver 204, digital signal processor 208, and controller 210 mayinclude separate components or instances dedicated to different radiocommunication technologies and/or unified components that are sharedbetween different radio communication technologies. For example, in someaspects controller 210 may be configured to execute multiple protocolstacks, each dedicated to a different radio communication technology andeither at the same processor or different processors. In some aspects,digital signal processor 208 may include separate processors and/orhardware accelerators that are dedicated to different respective radiocommunication technologies, and/or one or more processors and/orhardware accelerators that are shared between multiple radiocommunication technologies. In some aspects, RF transceiver 204 mayinclude separate RF circuitry sections dedicated to different respectiveradio communication technologies, and/or RF circuitry sections sharedbetween multiple radio communication technologies. In some aspects,antenna system 202 may include separate antennas dedicated to differentrespective radio communication technologies, and/or antennas sharedbetween multiple radio communication technologies. Accordingly, whileantenna system 202, RF transceiver 204, digital signal processor 208,and controller 210 are shown as individual components in FIG. 3, in someaspects antenna system 202, RF transceiver 204, digital signal processor208, and/or controller 210 can encompass separate components dedicatedto different radio communication technologies.

Accordingly, RF transceiver 204 and baseband modem 206 (including thedigital signal processor 208 and controller 210) may collectively bereferred to as cellular modem 218.

FIG. 3 shows an example in which RF transceiver 204 includes RFtransceiver 204 a for a first radio communication technology, RFtransceiver 204 b for a second radio communication technology, and RFtransceiver 204 c for a third radio communication technology. Likewise,digital signal processor 208 includes digital signal processor 208 a forthe first radio communication technology, digital signal processor 208 bfor the second radio communication technology, and digital signalprocessor 208 c for the third radio communication technology. Similarly,controller 210 may include controller 210 a for the first radiocommunication technology, controller 210 b for the second radiocommunication technology, and controller 210 c for the third radiocommunication technology. RF transceiver 204 a, digital signal processor208 a, and controller 210 a thus form a communication arrangement (e.g.,the hardware and software components dedicated to a particular radiocommunication technology) for the first radio communication technology,RF transceiver 204 b, digital signal processor 208 b, and controller 210b thus form a communication arrangement for the second radiocommunication technology, and RF transceiver 204 c, digital signalprocessor 208 c, and controller 210 c thus form a communicationarrangement for the third radio communication technology. While depictedas being logically separate in FIG. 4, any components of thecommunication arrangements may be integrated into a common component.

Terminal device 102 may also include application processor 212, memory214, and power supply 212. Application processor 212 may be a CPU, andmay be configured to handle the layers above the protocol stack,including the transport and application layers. Application processor212 may be configured to execute various applications and/or programs ofterminal device 102 at an application layer of terminal device 102, suchas an operating system (OS), a user interface (UI) for supporting userinteraction with terminal device 102, and/or various user applications.The application processor may interface with baseband modem 206 and actas a source (in the transmit path) and a sink (in the receive path) foruser data, such as voice data, audio/video/image data, messaging data,application data, basic Internet/web access data, etc. In the transmitpath, controller 210 may therefore receive and process outgoing dataprovided by application processor 212 according to the layer-specificfunctions of the protocol stack, and provide the resulting data todigital signal processor 208. Digital signal processor 208 may thenperform physical layer processing on the received data to producedigital baseband samples, which digital signal processor may provide toRF transceiver 204. RF transceiver 204 may then process the digitalbaseband samples to convert the digital baseband samples to analog RFsignals, which RF transceiver 204 may wirelessly transmit via antennasystem 202. In the receive path, RF transceiver 204 may receive analogRF signals from antenna system 202 and process the analog RF signals toobtain digital baseband samples. RF transceiver 204 may provide thedigital baseband samples to digital signal processor 208, which mayperform physical layer processing on the digital baseband samples.Digital signal processor 208 may then provide the resulting data tocontroller 210, which may process the resulting data according to thelayer-specific functions of the protocol stack and provide the resultingincoming data to application processor 212. Application processor 212may then handle the incoming data at the application layer, which caninclude execution of one or more application programs with the dataand/or presentation of the data to a user via a user interface.

Memory/storage 214 may embody a memory and/or storage components ofterminal device 102, such as a hard drive or another such permanentmemory device. Although not explicitly depicted in FIG. 2, the variousother components of terminal device 102 shown in FIG. 2 may additionallyeach include integrated permanent and non-permanent memory components,such as for storing software program code, buffering data, etc.Memory/storage 214 may include a plurality of different componentsincorporated into terminal device 102, each of which serve differentfunctions. For example, flash memory or a solid-state disk may beconnected to the Applications Processor 212 and function as storage.Also, there may be Double data rate synchronous dynamic random-accessmemories (DDR SDRAMs) connected to the Application Processor 212 and thebaseband modem processor. The whole software image (e.g. operatingsystem, application layers, and modem software) may be stored, forexample, in flash memory and loaded into the respective DDR-SDRAMsduring boot. The processors of the Application Processor and/or thebaseband modem may then execute the instructions from the DDR-SDRAM(s).

Power supply 216 may be an electrical power source that provides powerto the various electrical components of terminal device 102. Dependingon the design of terminal device 102, power supply 216 may be a‘definite’ power source such as a battery (rechargeable or disposable)or an ‘indefinite’ power source such as a wired electrical connection.Operation of the various components of terminal device 102 may thus pullelectrical power from power supply 216.

In accordance with some radio communication networks, terminal devices102 and 104 may execute mobility procedures to connect to, disconnectfrom, and switch between available network access nodes of the radioaccess network of radio communication network 100. As each networkaccess node of radio communication network 100 may have a specificcoverage area, terminal devices 102 and 104 may be configured to selectand re-select between the available network access nodes in order tomaintain a strong radio access connection with the radio access networkof radio communication network 100. For example, terminal device 102 mayestablish a radio access connection with network access node 110 whileterminal device 104 may establish a radio access connection with networkaccess node 112. In the event that the current radio access connectiondegrades, terminal devices 102 or 104 may seek a new radio accessconnection with another network access node of radio communicationnetwork 100; for example, terminal device 104 may move from the coveragearea of network access node 112 into the coverage area of network accessnode 110. As a result, the radio access connection with network accessnode 112 may degrade, which terminal device 104 may detect via radiomeasurements such as signal strength or signal quality measurements ofnetwork access node 112. Depending on the mobility procedures defined inthe appropriate network protocols for radio communication network 100,terminal device 104 may seek a new radio access connection (which maybe, for example, triggered at terminal device 104 or by the radio accessnetwork), such as by performing radio measurements on neighboringnetwork access nodes to determine whether any neighboring network accessnodes can provide a suitable radio access connection. As terminal device104 may have moved into the coverage area of network access node 110,terminal device 104 may identify network access node 110 (which may beselected by terminal device 104 or selected by the radio access network)and transfer to a new radio access connection with network access node110. Such mobility procedures, including radio measurements, cellselection/reselection, and handover are established in the variousnetwork protocols and may be employed by terminal devices and the radioaccess network in order to maintain strong radio access connectionsbetween each terminal device and the radio access network across anynumber of different radio access network scenarios. Or, for example,terminal devices 102 or 104 may seek to switch to enhanced coverage fromnormal coverage if the respective network access node on which they arecamped on supports enhanced coverage. By switching to enhanced coveragemode, terminal device 102 or 104 may increase the repetition insignaling with their respective network access node and/or increasesignal transmission power to improve communications.

As previously indicated, network access nodes 110 and 112 may interfacewith a core network. FIG. 4 shows an exemplary configuration inaccordance with some aspects where network access node 110 interfaceswith core network 402, which may be a cellular core network. Corenetwork 402 may provide a variety of functions essential to operation ofradio communication network 100, such as data routing, authenticatingand managing users/subscribers, interfacing with external networks, andvarious network control tasks. Core network 402 may therefore provide aninfrastructure to route data between terminal device 102 and variousexternal networks such as data network 404 and data network 406.Terminal device 102 may thus rely on the radio access network providedby network access node 110 to wirelessly transmit and receive data withnetwork access node 110, which may then provide the data to core network402 for further routing to external locations such as data networks 404and 406 (which may be packet data networks (PDNs)). Terminal device 102may therefore establish a data connection with data network 404 and/ordata network 406 that relies on network access node 110 and core network402 for data transfer and routing.

The methods and devices of this disclosure provide for power managementmechanisms for improving system performance.

As the complexity of System on Chips (SoC) continues to increase, thePeak Power (Pmax) requirements of these more complex and capable SoCwill continue to increase as well.

Reducing the SoC peak power budget can have a significant impact on theSoC's operating frequency. Since SoC power is highly dependent on systemworkload, it can peak unpredictably and virtually instantaneously. Toensure that SoC power never exceeds its Pmax budget allocation, itsoperating frequency has to be proactively controlled/limited to ensurethat any power spike does not violate the Pmax limit.

Platform peak power budget is allocated to a terminal device's manydifferent components, including, for example, display; cameras; modemand connectivity (e.g. 206, 204 in FIG. 2); memory and storage (e.g. 214in FIG. 2); and the SoC (i.e. the application processor, e.g. 212 inFIG. 2). These components each have respective Pmax power levels and canpeak independently of each other on very short time scales, e.g. inmicroseconds. While it is unlikely, from a statistical probabilitystandpoint, that all system components will exhibit a power peak at thesame time, given that component peak power is not controlled, currentsystems take a conservative approach and calculate system Pmax as thesum or some function (e.g. root mean square (RMS) function) of all ofits components' peak power (i.e. highest peak power). While thisapproach affords protection, it comes with significant loss in systemperformance by sacrificing power.

FIG. 5 is a graph 500 showing the power margin between Pmax limit andthe normalized platform operating power in current systems employing theworst case approach to protect against Pmax events in some aspects. Thisunder-voltage protection margin is shown by 502. The solid line showsthe platform power capability, while the dashed line shows the powerbudget allocated by current systems. The y-axis has been normalized withrespect to a full state of charge.

For example, at 50% state of charge, platform power delivery hasapproximately 0.6 of normalized power capability, however, the platformpower budget available for executing the average system workload is set(controlled) not to exceed 0.25 of the normalized power capability toaccount for worst case peak power events across all system components.Even though such events are highly unlikely, and often not evenpossible, the lack of Pmax control of platform components forces theentire system to operate at a much lower level of performance to protectagainst under-voltage events that can abruptly shut down the system.

Cellular modem operation can be characterized by a wide range of peakpower consumption levels for different typical cellular modem workloadstriggered by external events, e.g. network events, over time scales ofmilliseconds. The timing of these network events is unpredictable fromthe terminal device (i.e. platform) perspective because the base station(e.g. eNodeB) scheduler controls when the cellular modem (e.g. for LTE)enters a peak power consumption workload, e.g. max throughput (t-put)downlink allocation or uplink grants at maximum transmit power level. Asa result, the peak power budget allocated to the cellular modem incurrently implemented platforms is typically based on a conservativecorner cellular modem use case (e.g. sustained theoretical peakthroughput at maximum transmit power level) and worst case operating andenvironmental conditions (e.g. high ambient temperatures).

Other approaches, in addition to the sum of the component’ peak powerdescribed above, for computing platform Pmax include computing theaverage and root mean square (RMS) of the Pmax for all of thecomponents. However, these approaches implement a protection margin aswell, thereby leaving considerable amounts of power to go unused in mostreal-world scenarios which degrades overall system performance.

In some aspects, devices and methods dynamically manage the terminaldevice's peak power by following cellular modem 218 peak powerconsumption envelopes. A runtime peak power (Pmax) consumption estimator(implemented as hardware, software, or a combination) dynamicallydetermines upcoming cellular modem peak power consumption events byobserving internal protocol stack and physical layer state variables.This cellular modem Pmax estimator maps the upcoming events to apre-defined cellular modem peak power state, e.g. implemented by one ormore Look up Tables (LuTs) or using machine learning techniques topredict power demand and notify a platform (i.e. terminal device, UE)peak power manager (PPPM) about the upcoming cellular modem peak powerdemand. The Pmax estimator may therefore be configured with algorithmsto calculate the Pmax during run-time based on the cellular modem statevariables, such as the connected RAT (e.g. LTE). LuTs may, for example,be implemented where the algorithms are executed off-line. The PPPMdynamically determines the difference between the quasi-static worstcase modem peak power budget and the modem's upcoming peak power demandand reclaims the peak power budget not used by the cellular modem andre-allocates it to other platform components, e.g. to a SoC (i.e.application processor). Similarly, if the modem's upcoming power demandincreases, the power appropriate amount of power budget is reclaimedfrom the SoC and re-allocated to the cellular modem.

In some aspects, devices and methods are configured to predict futurepeak power consumption demand of a cellular modem. Modem peak powerconsumption is estimated during runtime by providing predictions ofupcoming peak power consumption demand at least few tens of millisecondsbefore the power consumption peak actually occurs. A modem consumptionmodel may be modeled as a function of the modem's internal statevariables, in particular, at least one of: the connected Radio AccessTechnology (RAT), for example, LTE; Radio Resource Control (RRC) state;number of component carriers (CCs, which may be frequency carriers,timeslots in TDMA systems, a set of codes in CDMA systems, etc.);transmit (Tx) power levels which may include using parameters for powerheadroom and/or pathloss; indications which may provide information onPmax consumption states including those from the Application Processoror Packet Data Convergence Protocol (PDCP) for uplink data to betransmitted along with its buffer size, RLC or MAC level indicationsincluding scheduling requests, or buffer status reports; number ofdownlink and/or uplink CCs; dynamic activation/de-activation of the CCsby the network; the Modulation Coding Scheme (MCS); Band information; orconnected discontinuous reception cycle (C-DRX) state entry and/or exitindications from firmware to the Pmax estimator.

In some aspects, devices and methods are configured to predict modempeak power consumption based on thermal context information. The modemPmax estimator considers modem throttle states and enhances the cellularmodem peak power consumption demand protection with thermal stateinformation from a modem thermal manager. The PPPM may be configured torequest the cellular modem to enter a throttled state and reduces thecellular modem Pmax demand in order to reallocate parts of the cellularmodem platform power budget to other platform components, e.g. the SoC(i.e. application processor). A modem thermal manager exposes printedcircuit board (PCB) cross-component thermal resistances to the PPPM toevaluate cross heating effects between different platform (i.e. terminaldevice) components to ensure that any released cellular modem powerbudget is re-allocated to components having a lower thermal couplingwith the modem.

In some aspects, a Pmax management mechanism allows the modem todynamically determine its Pmax requirements and communicate them to aPlatform Peak Power Manager (PPPM) which is configured to reallocate thereported unused budget to other system components (e.g. SoC, i.e.application processor). This enables the terminal device to minimize (orremove completely) the modem Pmax protection margin (e.g. as shown inFIG. 6) and improve overall system performance.

The PPPM methods and devices exhibit an improvement in processorfrequency for when the modem Pmax budget is reduced in a 2-for-1 clientplatform. By configuring the device with a PPPM mechanisms describedherein, the SoC (i.e. Application processor) is allocated power which isinitially allocated to but unused by the modem, resulting in anoticeable increase in operating frequency of the SoC withoutcompromising or weakening the overall system Pmax protection.

In some aspects, peak power (Pmax) management devices, algorithms andmethods are provided in which a cellular modem is configured todynamically compute its Pmax requirements and communicate them to aPlatform Peak Power Manager (PPPM) and/or hardware (HW) power manager(HWPM). The PPPM is configured to manage slow peak power events (e.g. inthe range of hundreds of milliseconds to seconds). These events mayinclude, for example, turning the modem device on or off, transitioningfrom one network type to another (e.g. from LTE to 2G), etc. The HWPM isresponsible for faster peak power events which need to be managed withinsmaller timescales, e.g. changes in transmit power or carrieraggregation requirements.

FIG. 6 shows a schematic diagram of a platform peak power manager (PPPM)600 in some aspects. It is appreciated that diagram 600 is exemplary innature and may thus be simplified for purposes of this explanation.Modem 620 may correspond to cellular modem 218 and SoC 630 maycorrespond to Application Processor 212 in FIG. 2, respectively. Thecomponents shown in diagram 600 may be implemented as hardware,software, or any combination thereof, in a platform, e.g. in terminaldevice 102.

The PPPM 602 is configured to compute the platform Pmax budget andallocate it among different platform components and the SoC, and it maybe implemented in software, firmware, platform hardware, or anycombination thereof. Software implementations may include platformdriver, operating system (OS) service or software middleware/framework.PPPM 602 is configured to receive or compute the Pmax based oninformation provided by the battery Fuel Gage (FG) 612 and/or thecharger 614. The exact value of platform Pmax may depend on one or morefactors, including, for example: battery state of charge, voltage,temperature, system resistance, etc.

Once Pmax is computed, the PPPM 602 computes the Rest of Platform Peakpower budget (RoPPL4). This budget depends on the peak powerrequirements of different platform components (device PL4, i.e. dPL4).In the case of modem 620, its peak power is computed based on the stateof the device and the type of network it is currently connected to. Whenpeak power requirements change (e.g. a user selects Airplane mode andturns the radio off or the network changes in between LTE and 2G), themodem 620 computes its new peak power (new Pmax) demand and provides itto the PPPM 702. The PPPM 602 uses the new Pmax request from the modem620 to update its RoP-PL4 budget. Every time the RoP-PL4 or platformPmax budget changes, the PPPM 602 computes a new SoC Pmax budget (PL4)and provides it to the HWPM 604. The HWPM 604 uses the PL4 to limit itsoperating frequency to ensure the SoC never exceeds its Pmax allocation.

The PPPM 602 is configured to ensure that platform Pmax is neverexceeded by managing Pmax transitions of different platform componentsand the SoC. When the modem 620, for example, requests more Pmax, thePPPM 602 first computes the new RoP-PL4 and PL4 values, updates the SoC630 with the lower PL4 and then allows the completion of the modemrequest. The PPPM 602 is responsible for managing slow Pmax changes thatare triggered either by user actions or events that occur infrequentlyand can be delayed or blocked for several tens of milliseconds or more.As such, the PPPM 702 is configured to converge on stable values forPmax, RoP-PL4 and PL4 which remain valid for several seconds and, intypical cases, perhaps even much longer.

While the PPPM 602 is configured to manage slow modem events, it may notbe able to respond to peak events that occur more frequently and cannotbe delayed for more than several milliseconds. For example, in currentimplementations, if a modem is enabled and attached to a LTE network,its peak power allocation is 5 W. However, peak power events are rarewith a modem typically only needing in the range of 1 W-5 W of peakpower allocation while in LTE connected mode depending on networkconditions and throughput demand. Therefore, constantly allocating 5 Wfor modem Pmax budget is inefficient since the device does notnecessarily need or use this allocated power budget for most of thetime. For example, while in idle or sleep mode, the modem requires onlyapproximately 0.5 W.

To address this misappropriation of power, the PPPM 602 is configured todynamically compute modem Pmax demand and provide it to the SoC 630(e.g. through the HWPM 604) in order to account for rapid changes in themodem Pmax demand based on changes in network conditions or carrieraggregation configurations as previously discussed. Furthermore, therequest to change the modem Pmax cannot be delayed for more than a fewmilliseconds before the modem experiences the actual power peak.

In some aspects, to quickly respond and manage these fast Pmax changes,the PPPM 602 is configured to employ a determined a PL4-Offset valuewhich represents the difference between the slow Pmax budget provided bythe modem 620 to the PPPM 602 and the modem's 620 current Pmax demand.For example, using the LTE 5 W example from before, if the modem 620determines that its current Pmax requirement is 1 W (for example, whenit is in LTE RRC idle mode state), the PPPM 602 may determine the newPL4-Offset and set it to 4 W.

Once the new PL4-Offset value is computed, it is sent to the HWPM 604which manages fast peak power events in the SoC 630. The new PL4-Offsetvalue with a modem device ID (device ID, or DID) can be sent overplatform management interfaces (e.g. PMSB) or a bus (e.g. I2C) eitherdirectly to the SoC 630 or through a chipset that supports a platformmanagement bus interface (e.g. a Platform Controller Hub, PCH). When theSoC 630 receives the new PL4-Offset value, it updates its PL4 level,thus reclaiming (or giving back) Pmax budget that is not currently usedby the modem 620. Continuing the example from above, the SoC 630 wouldincrease its Pmax allocation by 4 W. The PL4-Offset value in the SoC isupdated when a new modem Pmax change occurs and it is cleared when thePPPM 602 updates the PL4. In some aspects, a first power value used bythe communication device in allocating power may include the Modem dPL4and/or PL4-Offset.

FIG. 7 shows a schematic diagram 700 of a cellular modem 218 with amodem Pmax estimator 702 in some aspects. It is appreciated that diagram700 is exemplary in nature and may thus be simplified for purposes ofthis disclosure.

The RAT-specific modem, which for purposes of FIG. 7 is shown as the LTEmodem (204 a, 208 a, 210 a), reacts to events from the network or theuse, e.g. RRC-connection establishment. Cellular modem 218 operation canbe characterized by a wide range of modem Pmax consumption levels fordifferent types of modem activities (across different types of modems,e.g. also 2G, 3G, etc.) triggering these network events over timescalesof milliseconds, e.g. random access channel (RACH) procedure orreception of downlink (DL) data packets. In some aspects, the Modem PmaxEstimator 702 is configured to distinguish these activities duringruntime by observing the LTE modem (204 a, 208 a, 210 a) internal statevariables. Interfaces to the different cellular modem components (e.g.204 a, 208 a) are implemented, e.g. at the PHY layer which maps to theDSP 208 a and the cellular protocol stack to controller 210 a. Thesevariables, for example, may include the radio access technology (RAT),e.g. LTE or 2G; the number of DL component carriers (CC); transmit (Tx)power levels; indications from the Application Processor/PDCP; etc.(including other parameters discussed herein). Additional internal statevariables, such as those from the RF transceiver 204 or other thermalstate variables, may also be observed. The Modem Pmax Estimator 702 usesthese variables to provide modem Pmax demand at an interface to the PPPM804. Modem Pmax Estimator 702 may be implemented into baseband modem 206as software, firmware, hardware, or any combination thereof, and may beconfigured to estimate the modem Pmax levels by using a Look Up Table(LuT), or may also be implemented as a model to predict the power demandusing machine learning techniques by utilizing previously mentionedmodem internal parameters as machine learning or deep learning model's(e.g. Neural networks CNN/DNN/RNN/RBMs) input parameters and fitting themodel on historical modem data (i.e. from modem lab/field test results)to predict more fine granular power demands. An exemplary LuT showingmodem Pmax levels for modem-specific activities is shown in Table 2.These values may be, for example, determined at the time of modemdevelopment and stored in a LuT in the device. In some aspects, the LuTor machine learning model may be updated through software updates at thecommunication device.

TABLE 2 LTE modem Pmax model LuT Modem RRC State Pmax Level Activity RRCidle mode 1 W Idle (attached &default EPS¹ bearer established) RRCconnected active, 1 W Data call, 1 CC 20 MHz, single CC max t-put², cellcenter: 0 dB tx 3 W Data call, 1 CC 20 MHz, max t-put, cell edge: 23 dBtx 4 W Margin stacking for impedance antenna mismatch RRC connectedactive, 2 W Data call, 3 CC 60 MHz, three CCs max t-put, cell center 4 WData call, 3 CC 60 MHz, max t-put, cell edge 5 W Margin stacking forimpedance antenna mismatch ¹Evolved Packet System ²maximum throughput

As can be seen in Table 2, the different Pmax levels of the modem,ranging from 1 W to 5 W, show that the modem (in most cases) requiresless power than the normally allocated 5 W to account for the worst casescenario. Radio channel conditions may also impact the modem Pmaxlevels, as shown in Table 2, for example, location of the device in thecell (center vs. edge). However, radio channel conditions may alsoinclude antenna height, weather, changes in antenna tilt, interference,whether the UE is outside or inside, etc., Accordingly, a new PL4-Offsetmay be dynamically determined in order to dynamically provide increasedpower to the SoC.

FIG. 8 shows a second schematic diagram 800 of a cellular modem 218 witha modem Pmax estimator 702 in some aspects. It is appreciated thatdiagram 800 is exemplary in nature and may thus be simplified forpurposes of this disclosure. Diagram 800 illustrates the first powervalue from the modem which is used to calculate the second power valuefor allocating power to other components of the terminal device. The LTECellular Protocol Stack is mapped to LTE controller 210 a (for example)and the PHY layer is mapped to LTE DSP 208 a of FIG. 2, for example.

In some aspects, modem Pmax estimator 702 is configured to estimate thePmax power consumption of a cellular modem 218 during modem runtime byproviding predictions of upcoming Pmax consumption demand at least fewof milliseconds before the power consumption peak actually occurs. Thesepredictions may be used by the PPPM 602 of a terminal device (e.g. 102)to increase/decrease the operating frequency of an application processor(i.e. SoC), therefore, for example, improving user experience ofapplication with a high computational load.

Cellular modem 218 operation (and more specifically, the operation of aRAT-specific modem such as LTE modem (204 a, 208 a, 210 a)) may becharacterized by a wide range of modem Pmax consumption levels fordifferent typical modem activities triggered by network events, such asthough shown in Table 2. In some aspects, the Modem Pmax Estimator 702is configured to define tight upper bounds for modem Pmax consumptionover time scales of milliseconds.

FIGS. 9 and 10 show exemplary graphs 900 and 1000 for typical LTE modemPmax consumption. Specifically, graphs 900 and 1000 show modem powerenvelopes 902 and 1002 for an LTE modem in idle and connected mode,respectively.

Graph 900 depicts an LTE idle mode during deep sleep and receiving apaging reception, as seen in the peak in modem power envelope 902.Dependent on the desired accuracy, modem Pmax estimator 702 may beconfigured to model the idle mode Pmax by a single peak power level(shown by dashed line 904 a) or may be further model the power envelope902 by decomposing it into separate power levels to account for thepaging burst and deep sleep phases (shown by solid line 904 b).

Graph 1000 depicts power envelope 1002 for an LTE TDD data call atmaximum throughput (t-put). Modem Pmax estimator 702 may be configuredto model the LTE TDD call Pmax with line 1004.

In some aspects, the approach that the modem Pmax estimator 702 takes todetermine the modem power envelopes may include reducing the granularityof the modem Pmax levels to match a required resolution of thePL4-Offsets in the platform. For example, modem power levels in 1 Wsteps may be used. The approach may further include selecting dominatingmodem power consumption model parameters from modem internal statevariables. For example, the connected RAT, a Radio Resource Controlprotocol (RRC) state or the like, number of DL CCs, transmit (Tx) powerlevels, and the other parameters discussed herein may be used todistinguish modem Pmax levels of a particular modem. It is appreciatedthat this list is not exhaustive, and other modem internal statevariables may also be considered in determining the modem powerconsumption model. The approach may further include adding margin to themodem Pmax levels to cover power variations due to secondary parameters,such as, for example, DL and uplink (UL) throughput, antenna mismatch,or thermal considerations. Secondary parameters may be modem internalstate variables that cannot be predicted few tens of milliseconds inadvance, e.g. UL grants or DL allocations, or other parameters, such asthermal parameters (e.g. on-die junction temperatures). The separationof dominating modem internal state variables and these secondary modelparameters may be refined depending on modem design and configuration.

FIG. 11 is a diagram 1100 showing a mapping of modem operation to modemPmax demand in some aspects. It is appreciated that diagram 1100 isexemplary in nature and may thus be simplified for purposes of thisdisclosure. For example, diagram 1100 shows a process by which a ModemPmax Estimator is configured to operate with respect to an LTE connectedstate and using a LuT, but it is appreciated that the ensuingexplanation is equally applicable to other RATs and/or idle states, andalso using machine learning models in place of LuTs. Accordingly, otherconnected states (e.g. on 2G) may have corresponding LuTs and/or machinelearning models specifically tailored to their respective powerconsumption requirements.

Diagram 1100 depicts the modem Pmax model as a function of modeminternal state variables, which in diagram 1100, are shown as radioaccess technology (RAT), RRC state, number of DL CCs, and Tx powerlevel. The Modem Pmax Estimator may implement the model using a LuT,such as that shown in Table 2 or may also implement as a model topredict the power demand using machine learning or deep learningtechniques for example neural networks and its variants (e.g.DNN/CNN/RNN/RBM) by utilizing above mentioned parameters as model inputparameters and training the model on historical archived modem testingdata to predict more fine granular power demands for example at thegranularity of 0.5 Watt or even less. Such a model may be implemented byan algorithm, which in general, may include calculating modem Pmaxdemand runtime as opposed to using the LuT.

First, Modem Pmax Estimator 702 determines which RAT the cellular modemis currently connected to. In this example, the Modem Pmax Estimator 702determines that there is an active LTE connection 1102 (could also, forexample, be a 2G connection 1104; or an idle connection in any RAT, inwhich case 1 W may be used). Accordingly, the Modem Pmax Estimator 702is configured to use a LuT or machine learning model (e.g. an algorithmcalculating Pmax values runtime, in general) associated with connectedRAT, e.g. an LTE LuT shown as 1102 a. If the platform is activelyconnected in another RAT, then the LuT associated with that RAT is used.Once the appropriate LuT is obtained, the Modem Pmax Estimator 702 mayuse other internal state variables to select the most appropriate valueto send to the PPPM 602. In this example, since a Tx power of 23 dBm and1 CC is observed, the Modem Pmax Estimator 702 determines that 3 W is anappropriate Pmax value 1250.

One thing of note is that while the different Pmax levels are describedin these examples are shown as being in 1 W increments, it isappreciated that other levels of granularity may be employed, forexample, in 0.5 W increments, as seen in the first column, second row of1102 a (may elect 1.5 W instead of 2 W).

The Modem Pmax Estimator 702 may also be configured to dynamically reactto cellular network events, e.g. RRC connection establishment, anddetermine the Pmax level of the triggered activity, e.g. RACH procedureor DL grants. Other common network events triggering potential modemPmax state transitions may include, but are not limited to: measurementsfor cell re-selection in RRC idle mode, tracking area update (TAU), andtransmit power control during active connection. At trigger events suchas these, the LTE modem (204 a, 208 a, 210 a) (or other RAT-specificmodem) is configured to predict the Pmax demand of the upcoming activityaccording to the modem Pmax model of some aspects of the disclosureherein. In general, however, the LTE modem (204 a, 208 a, 210 a) canneither predict the duration of the activity nor the exact timing of thetrigger events because these depend on end user and network behavior.

The Modem Pmax Estimator 702 may be configured to transition to theappropriate Pmax state, i.e. select the right Pmax level, during runtimebased on internal state variables which are continuously updated bymechanisms built into the 3GPP standard: RRC state changes, adding orreleasing secondary cells (representing the number of CCs), powerheadroom reports below or above certain pre-defined thresholds(representing Tx power levels), and other parameters discussed herein.These state transitions typically happen several milliseconds and up totens of milliseconds prior to the power consumption peak actuallyoccurring.

FIG. 12 shows an exemplary graph 1200 of a modem event timing and Pmaxlevels for a mobile terminated (MT) LTE data call in some aspects.

The different Pmax levels (PwL1, PwL2, and PwL 3) are shown along they-axis and the time domain is shown on the x-axis of graph 1200,respectively (where K is any integer greater than or equal to 0). PwL1is the modem Pmax level for LTE RRC idle mode (e.g. 1 W), and PwL2 andPwL3 designate different modem Pmax levels for RRC connected mode, e.g.1 W and 3 W for single CC 20 MHz LTE data call at 0 dBm and 23 dBm Txpower levels, respectively. The transition from PwL1 to PwL2 or 3 istriggered when RRC connection establishment is initiated after the UEhas been paged by the network.

In some aspects, the immediate reporting of a new modem Pmax demand tothe PPPM 602 may be done at every state transition of the Modem PmaxEstimator 702. Worst case scenarios in terms of modem Pmax demand changerate are handover and connection re-establishment with standardizeddeadlines between 50 ms and 100 ms for completion of 3GPP procedures,resulting in 2 or more modem Pmax demand changes in about 100 ms, asshown in graphs 1300 and 1350 of FIG. 13.

Graph 1300 shows the worst case Pmax event for handover, and graph 1350shows the worst case Pmax event for connection re-establishment. In bothgraphs, the first event is a trigger for a respective procedure, e.g.the release of the secondary cell (SCell); the second event is thecompletion of the triggered respective procedure, e.g. completion of theRACH procedure and a new Tx power level on the new primary cell (PCell);and a third event in the re-establishment procedure which may include anRRC connection reconfiguration, e.g. the addition of a new SCell. Thisthird event, i.e. the rrcConnectionReconfiguration message, will occurafter a successful re-establishment procedure, but the UE may notreceive Scell addition in the rrcConnectionReconfiguration message(accordingly, the reception of such an addition may be optional).Furthermore, there is no timer (or the like) that after a certain timeinterval later the rrcConnectionReconfiguration message will be receivedby the UE.

In some aspects, the Modem Pmax Estimator 702 filters the reporting ofthese events to the PPPM 602 according to pre-defined SoC-Cellular modeminterface agreement requirements, e.g. according to a maximum allowedmodem Pmax demand change rate.

In some aspects, the Modem Pmax Estimator 702 may be configured toutilize thermal context information, e.g. on-die temperatures or printedcircuit board (PCB) temperature provided by thermal sensors, in additionto the aforementioned modem state internal variables to enhance the wayit estimate Pmax consumption of a cellular modem 218 during runtime inorder to provide predictions of upcoming Pmax consumption demand severalmillisecond up to tens of milliseconds prior to the power consumptionpeak actually occurring. These predictions may be used by a PPPM 602 ofa terminal device to, for example, increase/decrease an operatingfrequency of an application processor (i.e. SoC), thereby furtherimproving user experience of applications with high computational loads.

FIG. 14 shows a schematic diagram 1400 of a cellular modem 218 with aModem Pmax Estimator 702 and a Thermal Manager 1402 in some aspects. Itis appreciated that diagram 1400 is exemplary in nature and may thus besimplified for purposes of this disclosure. It is appreciated thatfeatures of diagram 1400 are similar to other diagrams (e.g. in FIGS. 7and 8) and thus are not discussed in detail with respect to FIG. 14.

RAT modem chips such as LTE modem (204 a, 208 s, 210 a) are embeddedwith temperature sensing and data throttling capabilities that arecontrolled by Thermal Manager 1402, which may be implemented insoftware, hardware, firmware, or any combination thereof, in cellularmodem 218. For example, in long duration LTE RRC connected states,self-heating may drive the cellular modem 218 towards its temperaturelimits. In such scenarios, the modem 218 has to limit/reduce its powerlevel for a time (e.g. multiple seconds) in order to allow for passivecooling of the subsystem in order to avoid problems such as hitting thechip thermal runaway temperature. The cellular modem 218 peak powerconsumption is a function of a plurality of internal state variables,including thermal information and throttling states. During this timespan, power budget will be released from the modem 218 which can bere-allocated to other components, e.g. the SoC/Application Processor, ofthe platform (i.e. terminal device 102). Also, once the modem 218returns from its imposed temperature limited state, it may resume onhigh data traffic, and accordingly, its power budget must be increasedagain to higher levels, e.g. its full power budget.

Thermal manager 1402 is configured to observe the baseband modem'sthermal environment and provide the PPPM 602 with information such ascross-component thermal resistance and modem throttle state transitions.

FIG. 15 is a graph 1500 showing modem temperature and throttle stateindications which may be provided by a Thermal Manager 1402 to the PPPM602 for dynamically allocating the power budget of a terminal device.

The Modem Temperature is shown by line 1502.

The time scales of each of t1-t4 are in the range of a couple ofseconds, thereby allowing for the use of throttling state parameters inre-allocating portions of the power budget intended for the modem toother device components, e.g. the Application Processor, Bluetooth,display, speakers, etc.

At Pmax indication 1 1512, a SLIGHT throttling state may be activated toaccount for the rising modem temperature 1502. One-third (for example)of the modem power budget is released for a minimum time of t2 (whiletemperature decreases back to a predetermined value). Accordingly, thisreleased portion of the power budget for time t2 may be reallocated toother device components by the PPPM 602.

At Pmax indication 2 1514, the temperature cooling is almostaccomplished, so a burst cycle may be enabled. The full budget for modemPmax will be required for t3.

At Pmax indication 3 1516, a SIGNIFICANT throttling state may beactivated to account for the rising modem temperature 1502 (Note: thisis illustrated by showing a higher temperature than that at Pmaxindication 1 1512). Two-thirds (for example, in any case, a higherportion than that for the SLIGHT throttling state) is then released fortime t4 in order to alleviate thermal concerns. Accordingly, thereleased portion of the power budget for time t4 may be reallocated toother device components by the PPPM 602.

In some aspects, an approach for implementing modem thermal informationfor more efficient terminal device power management is provided byaccounting for the current modem thermal budget. If the modem has a highthermal budget available, there may be no restrictions to enter modemoperation modes with high power consumption, e.g. data calls at maximumthroughput. If the modem thermal budget is almost consumed, certainoperation mode with higher power consumption may be blocked from beingexecuted by the modem. The approach may further include observing modemthrottle state information, which may indicate portions of the modempower budget which will not be used. The thermal manager 1502 may, forexample, define four modem throttle states: NONE (i.e. off), SLIGHT,SIGNIFICANT, and AGGRESSIVE. Each throttling state may include releasingportions of the modem power budget in increasing portions (e.g.AGGRESSIVE may release all or close to all, of the modem power budget).The approach may further include predicting a next burst data cycle andnext throttling cycle start plus duration. This information may allowthe PPPM 702 to update the quasi-static worst case modem Pmax budget.The approach may further include monitoring for indication signalsrelated to the modem needing a full power budget back within a certainamount of time, and the modem releasing a portion of the power budgetfor at least a certain amount of time (examples of which are explainedabove in explanation for FIG. 15).

In some aspects, the cellular modem 218 may send indication messages tothe PPPM 602 related to modem thermal budget during RRC connectedstates. These messages may include whether the modem is capable ofexploiting its full Pmax budget or whether its thermal capacity islimited for a given time period (i.e. in one of the throttle states fora given time period). These indication message may include a time periodwhich indicates to the PPPM 602 how long the power budget will be neededor when the next power budget update is to be expected. Also, the PPPM602 may be configured to request the cellular modem 218 to enter athrottled state, thereby reducing baseband modem Pmax demand in order tore-allocate parts of the modem power budget to other device components,e.g. SoC (i.e. the Application Processor).

As temperature changes over a time scale of seconds rather thanmilliseconds, signaling latency between the cellular modem 218 and theApplication Processor 212 (i.e. SoC) will have little to no performanceeffects. The use of thermal information will allow for the PPPM 602 tore-allocate parts of the modem power budget to other components of themobile device for longer durations, e.g. multiple seconds during phasesof passive cellular modem cooling due to throttling.

In some aspects, the Thermal Manager 1402 may expose printed circuitboard (PCB) cross-component thermal resistances to the PPPM 602 toevaluate cross heating effects between different mobile devicecomponents on the PCB. This may help to avoid the jeopardizing ofpassive modem cooling (i.e. throttling) when the released power budgetof a baseband modem subsystem (e.g. LTE modem 204 a, 208 a, 210 a) willbe re-allocated to another component which has an unfavorable heatingcoefficient versus the modem hotspot. The released modem power budgetmay instead be reallocated to components that have a lower thermalcoupling with the modem.

FIG. 16 shows another schematic diagram of an internal configuration ofcontroller 210 according to some aspects. As shown in FIG. 16,controller 210 may include processor 1602 and memory 1604. Processor1602 may be a single processor or multiple processors, and may beconfigured to retrieve and execute program code to perform thetransmission and reception, channel resource allocation, and clustermanagement as described herein. Processor 1602 may transmit and receivedata over a software-level connection that is physically transmitted aswireless signals or over physical connections. Memory 1604 may be anon-transitory computer readable medium storing instructions for one ormore of PPPM subroutine 1604 a, an HWPM subroutine 1604 b, a Modem PmaxEstimator subroutine 1604 c, and/or a thermal manager subroutine 1604 d.

PPPM subroutine 1604 a, an HWPM subroutine 1604 b, a Modem PmaxEstimator subroutine 1604 c, and/or a thermal manager subroutine 1604 dmay each be an instruction set including executable instructions that,when retrieved and executed by processor 1602, perform the functionalityof controller 206 as described herein. In particular, processor 1602executes PPPM subroutine 1604 a to implement aspects of the PPPM 602 asdescribed herein; processor 1602 may execute PPPM subroutine 1604 b toimplement aspects of the HWPM 604 as described herein; processor 1602may execute Modem Pmax Estimator subroutine 1604 c to implement aspectsof the Modem Pmax Estimator 702 as described herein; and/or processor1602 may execute Thermal Manager subroutine 1604 d to implement aspectsof the Thermal Manager 1402 as described herein. While shown separatelywithin memory 1604, it is appreciated that subroutines 1604 a-1604 d maybe combined into a single subroutine exhibiting similar totalfunctionality. By executing the one or more of subroutines 1604 a-1604d, a terminal device may be configured to dynamically manage its powerbudget in order to improve device performance.

FIG. 17 shows a flowchart 1700 according to some aspects. It isappreciated that flowchart 1700 is exemplary in nature and may thereforebe simplified for purposes of this explanation.

Flowchart 1700 illustrates a method for allocating power among aplurality of circuits in a communication device. In 1702, a power budgetis determined for allocating to the plurality of circuits from a powersupply information. In 1704, an activity status is received from a firstcircuit of the plurality of circuits. In 1706, a first power value isdetermined based on the activity status. In 1708, a second power valueis derived based on the first power value and the power budget. In 1710,power is allocated to one or more remaining circuits of the plurality ofcircuits based on the second power value.

In some aspects, devices and methods for configuring a plurality ofprocessing blocks (e.g. Fast Fourier Transform (FFT) processing circuitsor any processing blocks configured for signal transmission/receptionand/or application processing) on a chip of a communication devicespecific to a battery providing power to communication device may beimplemented. For example, battery discharge characteristics may beobserved and implemented into a battery discharge controller to provideimproved battery life of communication devices.

Wireless mobile communications continues to be one of the mostchallenging processing performance systems, implementing multiple unitsof heterogeneous and homogenous processing architectures including aplurality of processing blocks. In some aspects, partitioning ofhardware and software between serial and parallel resources is exploitedin order to improve overall device performance.

The capacity of NiMH, Li-Ion batteries may decrease in many differentmanners depending on the wide range of load conditions. For example, awide range of discharging modes are experiences due to loads ranginganywhere from constant, low loads to a high, pulsed loads. In terms ofoptimizing longevity, it is preferred to maintain a battery at moderatecurrent at a constant discharge rather than a pulsed (i.e. momentarilyhigh) load. Unfortunately, the usage scenarios in terminal devices (i.e.user equipment, UE) do not follow a single consistent scheme, andtherefore, the load conditions attributed to UE usage seldom remainconstant. Furthermore, battery types are generally designed either forlong duties/high endurance or for heavy load current, but they are notdesigned for both scenarios and the many load conditions occurring inbetween. This tradeoff between discharge capacities, load conditions,and battery types presents difficulties for battery-driven Internet ofThings (IoT) devices.

Battery discharge scenarios vary drastically due to the diverse loadpatterns of communication devices which leads to different impacts onbattery life, e.g. high load conditions where a battery discharges athigh C-rates, where 1 C is the discharge current that a battery candeliver for 1 hour before the battery voltage reaches the end-of-lifepoint, thereby decreasing the battery life expectancy. Therefore,operations which discharge a battery beyond the specifiedend-of-discharge voltage (EODV) need to be minimized, if not completelyeliminated. The EODV is a measured cell voltage to which a batterydischarge to where ˜95% of the stored energy is spent and the voltagewill drop rapidly if discharging continues. The EODV, in other words, isimplemented to prevent the battery from discharging beyond the specificvoltage. The EODCV is typically higher for normal loads than for higherloads and/or lower operating temperatures since high load currents (orlower temperatures) lower the battery voltage, so the EODV is set lowerto avoid premature cut-off. Therefore, the load should be adapted insuch a way to keep the battery state of charge around a midpoint voltage(MPV, the voltage is measured when the battery has discharged 50% of itstotal energy).

Therefore, in some aspects, the devices and methods herein providesolutions to the problem of controlling a terminal device (e.g. such asan IoT device, UE, etc.) in order to maintain it at an optimal workingpoint in terms of current drain (discharge) so that the batterydischarge time is prolonged, independent of the type of battery that isused. Current implementations include fixed and static number ofparallel and/or serial data processing blocks which operate in a mannerregardless of the effects of load balancing.

FIG. 18 shows a system 1800 implementing a rigid architecture. It isappreciated that system 1800 is exemplary in nature and may thus besimplified for purposes of this explanation. For example, while onlyseven processing blocks (1810-1816 and 1820-1824) are shown, it isreadily understood that the ensuing explanation applies to any number ofprocessing blocks, especially larger numbers.

In system 1800, four serial processing blocks (i.e. 1810-1816) and threeparallel blocks (i.e. 1820-1824) are implemented between input 1850 andoutput 1852. For example, system 1800 may be an Application Processor212 or a cellular modem 218 as shown in FIG. 2, respectively. Each ofthe processing blocks 1810-1816 and 1820-1824 may be components of anApplication Processor or a Baseband modem wherein each block isconfigured to perform one or more tasks, e.g. any type of wirelesssignal processing (e.g. such as FFT processing), application processing,graphics processing, etc. However, due to system's 1800 rigidarchitecture, there is no flexibility for manipulating its structure. Inother words, once produced, system 1800 will always have four serialprocessing blocks and three parallel processing blocks with no regardsto the characteristics of the battery it is subsequently connected tofor a power source.

Solutions such as those shown in system 1800 are optimized either for(1) long duties and high endurance, i.e. a constant current drain, or(2) heavy load currents, i.e. pulsed high current drain, but they arenot capable of being modified for one or the other due to their rigidarchitecture. These rigid systems attempt to maximize the batterydischarge time by achieving a very local optimum for a single loadcondition for a very specific battery type, and completely fail toaddress the dependency between current drain and batter capacity for thewide ranging load condition of IoT and the different battery types. Byimplementing the solutions and devices herein, a prolongation of up to25% in battery discharge time may be achieved.

In some aspects, devices and methods are configured to adapt a systemload by dynamically balancing between parallel and serial processing inorder to maximize performance in terms of battery state of chargethereby maximizing battery longevity. The methods and devices may scalethroughout the entire stack, including hardware and/or software.

In some aspects, the principles herein may be applied from Layer 1 (PHY)processing circuits up to the Application Layer where the execution ofapplications may be handled in parallel and/or serial configurations.Accordingly, the load balancing may protect a system against latency athigher communication layers, such as Radio Resource Control (RRC) andHypertext Transfer Protocol (HTTP), when properly designed and exploitedin parallel sub-systems.

In some aspects, methods and devices are configured to consider one ormore several factors, such as the effect of the battery currentdischarge rate on total processing capacity of a plurality of processingblocks of a chip based on a remaining battery capacity.

A first factor may be for a device to minimize the current drain overthe longest period of time. A switched on system always has a loadcondition with an average minimum current drain due to necessary basicfeatures (e.g. control functions, leakage, etc.). Accordingly, theenergy efficiency of system data and signal processing blocks ismaximized when this system average minimum current drain is as low aspossible.

A second factor may be for a device to minimize the amount of time itspends in high load conditions. A switched on system has highperformance load conditions with peak current drains due to dataprocessing data bursts, e.g. high throughput downlink data busts inwireless communications, high graphics loads in computer games, etc. Theenergy efficiency of the system data and signal processing blocks ismaximized when the system processes the data/signals as quickly aspossible while avoiding high current peaks which quickly discharges thebattery.

A third factor may be for a device to tailor a current drain to achievean optimum level and remain as constant as possible over time specificto a battery type. The capacity of a battery is significantly reducedwith increasing discharge current beyond a battery-specific optimaldischarge capacity but the discharge must stop before achieving thebattery-specific EODV.

In some aspects, devices and methods dynamically determine and set asystem's parallel and serial processing units (e.g. at the hardwarelevel or also in software), therefore satisfying the aforementionedfirst and second factors while reaching and retaining the battery stateof charge working point. This keeps the current drain as low, but alsoas close to the optimal working point for constant load conditions whilealso maintaining the current drain as high as is necessary (and as closeto the optimal working point) to account for peak load conditions. Thedevices and methods herein are able to implement these two conflictingrequirements by dynamically setting the system's parallel and serialprocessing units to battery characteristics, e.g. maintaining a workingpoint around the battery state of charge at the mid-point voltage,independent of processing load conditions, thereby maximizing batterycapacity and longevity.

FIGS. 19 and 20 show graphs 1900 and 2000, respectively, illustratingparameters for a Battery Discharge Controller (BDC) to account foraccording to some aspects. It is appreciated that graphs 1900 and 2000are exemplary in nature and may thus be simplified for purposes of thisdisclosure.

Graph 1900 shows a typical dependency between current drain and batterycapacity specific to a battery at a fixed voltage level. Differentcurrent drains (1 C to 18 C) are shown, where 1 C equals the current fordischarging the battery in one hour. As can be seen in graph 1900, athigher current drains (e.g. at 14 C and 18 C), the battery capacity isreduced.

However, batteries of different types may exhibit differentcharacteristics to different load conditions, i.e. different batteriesmay each have a unique set of curves as shown in graph 1900. Also,thermal characteristics (e.g. ambient temperature) may affect abattery's behavior. Accordingly, each battery type has characteristicswhich are different to other battery types. The characteristics (i.e.curves shown in graph 1900) specific to a particular battery may bepre-determined (e.g. in lab testing) and implemented/programmed into aBattery Discharge Controller (BDC).

Graph 2000 shows a typical dependency between average data processingversus peak performance current drain in a dedicated time slot. As canbe seen in graph 2000, higher data processing is achieved at a highercurrent drain up to a certain point, in which case the plurality ofprocessing blocks reaches a maximum limit of data processing (e.g. allthe processing blocks are running in parallel, or the maximum amount ofprocessing blocks considering thermal considerations is reached).

Taking into account that there is optimal discharge capacity (e.g. 1 C,1.2 C, i.e. any number greater than 0) for every battery type whichmaximizes the discharge time of the specific battery, the BDC isconfigured to identify this discharge current (or discharge currentrange) and maintain it by configuring the plurality of processing blocksin the appropriate manner (i.e. setting the number of processing blocksoperating in parallel and those operating in series so that theidentified current is maintained).

FIG. 21 shows a graph 2100 illustrating a function that a batterydischarge controller (BDC) may implement to determine discharge capacityfor a communication device according to some aspects. It is appreciatedthat graph 2100 is exemplary in nature and may thus be simplified forpurposes of this disclosure.

Graph 2100 illustrates an exemplary the dependency of the capacity ofdata processing (excluding base features, e.g. leakage) on batterydischarge current 2102. The x-axis is the battery discharge current andthe y-axis is the data processing capacity for a remaining charge of abattery (e.g. could be at full charge, i.e. 100%).

At the lower end, 2122, the dominating effect is that most of theaverage current drain is used for base features for long periods oftime. In this sense, if the battery discharge current is low, thecapacity for a plurality of blocks to process data is also low, and thelow discharge may only be sufficient to power on the plurality of blocksand not process very much data.

At the upper end, 2124, the dominating effect is that the batterycapacity is reduced at high current drain peaks. In this sense, at anygiven moment, the plurality of processing blocks may be able to processlarge quantities of data, but due to the high current drain, the batterymay discharge at a disadvantageously propionate rate with respect to thedata being processed.

Accordingly, the BDC is configured to take into account these factors inorder to maintain the system at a working point in range 2110 that is asclose to the optimum point 2110 a as possible, i.e. results in the mostdata being processed for a single battery charge. The BDC manages thisby controlling the serial and parallel processing split of theprocessing blocks in the system (e.g. a Network on Chip, NoC). The BDCselects the configuration depending on battery type such that theoverall load condition, and therefore the current drain, falls withinrange 2110, i.e. is as close to 2110 a as possible. For example,depending on the granularity of the processing blocks, BDC may not beable to select a current that is exactly at 2210 a, but may be able toselect a configuration within range 2110.

Among the configurations determined by the BDC to be available (e.g.taking different protocols in to account), the configuration of paralleland serial processing blocks exhibiting the tendencies closest to 2110 ais selected. This dynamic tailoring of the parallel and serialprocessing block configuration maximizes battery discharge time, therebyimproving user experience by increasing the availability that a terminaldevice (such as 102) may be used prior to being charged again. Forexample, the BDC is configured to determine when the capacity of aconfiguration lies to the left of range 2110, it increases the number ofparallel processing blocks in order to move the system into range 2110,and vice versa, the BDC is configured to determine when the capacity ofa configuration lies to the right of range 2110, it increases the numberof serial processing blocks in order to move the system into range 2110.

In wireless communication devices, base features always use currentwhile active (i.e. powered on), and during signal processing, forexample, fast signal processing is desired in order to shorten thelength of operation duration, i.e. high loads for short periods. This isdesired so as not to waste power on the base features while thecomponent is powered on. If there is no processing to be done by acomponent of a device, that component may be turned off in order toeliminate the base feature power consumption, e.g. in the case where aUE is not connected to an WiFi network, the WiFi signal processingcircuitry may be switched off, or during a discontinuous reception (DRX)cycle in LTE communications, the reception signal processing circuitrymay be powered off, etc.

Accordingly, the BDC is configured to take these factors into account inorder to minimize current drain peaks in order to maximize battery life,and also provide sufficient power for signal processing by setting theparallel/serial processing block configuration on a NoC.

FIG. 22 shows a schematic diagram of a Network on Chip (NoC) 2204 with aBattery Discharge Controller (BDC) 2202 according to some aspects. It isappreciated that schematic diagram 2200 is exemplary in nature and maythus be simplified for purposes of this disclosure.

While BDC 2202 is shown as being external to NoC 2204, it is appreciatedthat they be integrated so that BDC 2202 and NoC 2204 are included intoa single component (e.g. digital signal processor, applicationprocessor, etc.) of a communication device (e.g. terminal device 102).NoC is configured with a plurality of processing blocks in rows andcolumns (each of boxes #1,1 to #n, m; where n and m are any integersgreater than 2 and 3, respectively) which may be operatively connectedbetween an one or more inputs and one or more outputs 2212 (only one ofeach shown in FIG. 23). The BDC 2202 may be implemented as software,hardware, or any combination thereof. BDC 2202 may also include anoptional communication channel with a battery 2206 of a terminal devicein which it is implemented. In this manner, BDC 2202 may be configuredto receive information directly from battery 2206. Alternatively, BDC2202 may receive information from the battery through input 2210 and NoC2204. In either case, BDC 2202 is configured to identify the battery anduse the appropriate configuration in order to maximize systemperformance. This may be implemented using a Look up Table (LuT)programmed into a memory accessible by BDC 2302.

As shown in FIG. 22, each of the processing blocks may be arranged toprocess data/signals either serially or in parallel. The specificconfiguration (i.e. which blocks operate in serial vs parallel) is setby the BDC 2202.

Two exemplary configurations 2204 a and 2204 b of a plurality ofprocessing blocks are shown in FIGS. 23 and 24, respectively. Asdemonstrated, 2204 a may be implemented by BDC 2202 for systemsoperating with basic load conditions and 2204 b may be implemented byBDC 2202 for systems operating for peak load conditions. For basic loadconditions, a higher number of processing blocks will be configured tooperate serially as opposed to operating in parallel to ensure that amore constant current drain is maintained (i.e. using graph 2100, toensure that the device is within 2110 by moving along curve to theright). For peak load conditions, a higher number of processing blockswill be configured to operate in parallel as opposed to operatingserially to ensure that a more constant current drain is maintained byminimizing peak capacity drainage time (i.e. using graph 2100, to ensurethat the device is within 2110 by moving along curve to the left).

In some aspects, a BDC control loop is implemented to constantly monitorand/or analyze the current drain and allows for the BDC to adapt theparallel/serial execution as required in order to maintain the device inthe best operating mode.

In some aspects, BDC 2202 may be configured to operate in differentmodes.

In a first mode, herein referred to as “static mode,” the BDC 2202 isconfigured at manufacture and determined by a developer to be specificto a system, e.g. a NoC, and a battery type of a communication device inwhich it is implemented. In this mode, once the BDC is programmed withthe appropriate information, e.g. battery type and/or system type (e.g.a modem for a wireless protocol, e.g. LTE), it may set the processingblocks to operate in a configuration (including parallel and seriallyoperating blocks) to maintain the device in a specifically definedworking range for improving battery discharge and system performance.The BDC may determine which blocks are to operate either in parallel orserially at a given time according to a wireless protocol, i.e. forwhich time slots to activate one or more processing blocks in order toprocess received signals. Furthermore, the BDC 2202 may determine whichblocks to (digitally) switch off during given time slots to avoiddischarge through base features (e.g. leakage). Accordingly, in staticmode, once the BDC 2202 configures the configuration (e.g. on a NoC),the configuration is set.

For static mode, BDC 2202 may be implemented by using a Look up Table(LuT) programmed into a memory component accessible to the BDC 2202 (maybe internal or external) by the manufacturer/developer. Such informationmay include battery type and for what the system is to be used for, e.g.application processing, radio frequency (RF) signal processing, etc.

In a second mode, herein referred to as “dynamic mode,” the BDC 2202 isconfigured to dynamically alter the configuration of serial and parallelprocessing blocks. In this sense, the BDC 2202 is configured todynamically maintain the system as close to the optimal working point aspossible. The BDC 2202 may monitor the NoC, and adjust the configurationof processing blocks (serial and parallel executing blocks) based on theresults of the monitoring. This monitoring may be performed for timeperiods which are determined to provide a reliable assessment to the BDC2202. The BDC 2202 may then adjust the configuration of processing ofthe processing blocks during system downtime, e.g. during idle periodsin a discontinuous reception cycle (DRX), during RRC idle mode, duringdevice sleep mode, etc.

In some aspects, the BDC 2202 may be configured to digitally turn off oron processing blocks in order to maintain as constant a current drain aspossible.

In some aspects, the BDOC 2202 may be configured to use a pre-determinedset of parameters describing the relationship between total dataprocessing capacity of a remaining charge of a battery and a currentdischarge rate of the battery provided by, for example, a manufactureror developer, in order to set a configuration of a plurality ofprocessing blocks.

In some aspects, the BDOC 2202 may be further configured to reconfigurethe configuration of the plurality of processing blocks based on aninformation obtained during a monitoring of at least one of a battery orthe plurality of processing blocks.

In some aspects, the BDOC 2202 may be configured to reconfigure theconfiguration of processing blocks during a pre-determined time, e.g.during idle times in discontinuous reception and/or transmission cycles,while in RRC Idle mode, during night time hours, while the battery ischarging, or the like.

In an exemplary static mode implementation, the BDOC 2202 may configurefive FFTs to operate in parallel in one or more time slots (e.g.according to LTE downlink protocol) in order to achieve a current(battery discharge) to maintain the operating capacity in 2110 as shownin FIG. 21.

FIG. 25 shows a flowchart 2500 describing a method for battery dischargecontrol according to some aspects. Flowchart 2500 describes the methodfor operating a BDC in static mode.

In 2502, a function is derived which describes a remaining dataprocessing capacity dependent on battery current. This may be aremaining data processing capacity of a battery with a full charge. Insome aspects, this function may be provided to a battery dischargecontroller of a communication device by a manufacturer specific to thebattery type and the function of the plurality of processing blocks(e.g. if used for signal processing, or other functions of terminaldevice 102). An exemplary function is shown in FIG. 21.

In 2504, a range of battery current from the function is selected todeliver a desired data processing capacity. For example, this range maybe 2110 of FIG. 21, and even more specifically, it may be 2110 a.

In 2506, the BDC configures the one or more of the plurality ofprocessing blocks of the plurality of processing blocks based theselected range.

FIG. 26 shows a flowchart 2600 describing a method for battery dischargecontrol according to some aspects. The method described in flowchart2600 is supplemental to flowchart 2500, and further describes a methodfor operating a BDC in dynamic mode.

In 2602, at least one of a battery discharge information as the batterydischarge or the plurality of processing blocks at one or more batterystate of charges is monitored by the BDC.

In 2604, the BDC reconfigures the one or more processing blocks of theplurality of processing blocks based on the monitoring of the batterydischarge information or the plurality of processing blocks at one ormore battery state of charges. For exemplary purposes, this may includereconfiguring the operation of processing blocks between operatingserially or in parallel in order to maintain a battery discharge currentin 2110 of FIG. 21.

FIG. 27 shows another schematic diagram of an internal configuration ofBDC 2202 according to some aspects. As shown in FIG. 27, BDC 2202 mayinclude processor 2702 and memory 2704. Processor 2702 may be a singleprocessor or multiple processors, and may be configured to retrieve andexecute program code to perform the transmission and reception, channelresource allocation, and cluster management as described herein.Processor 2702 may transmit and receive data over a software-levelconnection that is physically transmitted as wireless signals or overphysical connections. Memory 2704 may be a non-transitory computerreadable medium storing instructions for one or more of Battery Functionsubroutine 2704 a, a Current Selection subroutine 2704 b, a Monitoringsubroutine 2704 c, and/or Configuration/Reconfiguration subroutine 2704d.

PPPM subroutine 2704 a, an HWPM subroutine 2704 b, a Modem PmaxEstimator subroutine 2704 c, and/or a thermal manager subroutine 2704 dmay each be an instruction set including executable instructions that,when retrieved and executed by processor 2702, perform the functionalityof BDC 2202 as described herein. In particular, processor 2702 executeBattery Function subroutine 2704 b to derive a function of a remainingdata processing capacity dependent on battery current (e.g. may bestored as a LUT); processor 2702 may execute Current Selectionsubroutine 2704 b to select a range of battery current from the functiondelivering a desired data processing capacity (e.g. within an range asshown in FIG. 22); processor 2702 may execute Monitoring subroutine 2704c to implement aspects dynamic mode of a BDC as described herein; and/orprocessor 2702 may execute Configuration/Reconfiguration subroutine 2704d to configure and/or reconfigure a plurality of processing blocks.While shown separately within memory 2704, it is appreciated thatsubroutines 2704 a-2704 d may be combined into a single subroutineexhibiting similar total functionality.

The following examples pertain to further aspects of this disclosure:

Example 1 is a communication device for allocating power among aplurality of circuits, the communication device including one or moreprocessors configured to determine a power budget for allocating to theplurality of circuits based on a power supply information; receive anactivity status from a first circuit of the plurality of circuits;determine a first power value based on the activity status; derive asecond power value based on the first power value and the power budget;and allocate power based on the second power value to a second circuitof the plurality of circuits.

In Example 2, the subject matter of Example(s) 1 may include the one ormore processor configured to obtain the power supply information from abattery of the communication device.

In Example 3, the subject matter of Example(s) 1-2 may include whereinthe power supply information comprises a state of charge of a battery ofthe communication device.

In Example 4, the subject matter of Example(s) 1-3 may include, whereinthe first circuit is a cellular modem.

In Example 5, the subject matter of Example(s) 4 may include wherein thecellular modem is configured to operate according on one or more radioaccess technologies (RATs).

In Example 6, the subject matter of Example(s) 5 may include wherein atleast one of the RATs is configured to operate according to a RadioResource Control (RRC) protocol.

In Example 7, the subject matter of Example(s) 6 may include the one ormore processor configured to determine the activity status based on thecellular modem's RRC state.

In Example 8, the subject matter of Example(s) 7 may include the one ormore processor configured to determine whether the RRC state is idlemode or in connected mode.

In Example 9, the subject matter of Example(s) 8 may include the one ormore processor configured to determine the first power value based onthe determination of the RRC state being in idle mode or connected mode.

In Example 10, the subject matter of Example(s) 5-9 may include the oneor more processor configured to determine a number of carriers beingused by the cellular modem.

In Example 11, the subject matter of Example(s) 10 may include the oneor more processor configured to determine the first power value based onthe number of carriers.

In Example 12, the subject matter of Example(s) 5-11 may include the oneor more processor configured to observe radio channel conditions.

In Example 13, the subject matter of Example(s) 21 may include the oneor more processor configured to determine a location based on a receivedsignal from a base station.

In Example 14, the subject matter of Example(s) 12-13 may includewherein the location is a cell center or a cell edge of a cell on whichthe communication device is camped on.

In Example 15, the subject matter of Example(s) 4-14 may include, theone or more processor configured to determine the first power valuebased on a transmit level of the cellular modem.

In Example 16, the subject matter of Example(s) 1-15 may include the oneor more processor configured to subtract the first power value from thepower budget in order to derive the second power value.

In Example 17, the subject matter of Example(s) 1-16 may include the oneor more processor configured to receive an updated activity status fromthe first circuit.

In Example 18, the subject matter of Example(s) 17 may include, the oneor more processor configured to determine an updated first power valuebased on the updated activity status.

In Example 19, the subject matter of Example(s) 18 may include the oneor more processor configured to derive an updated second power valuebased on the updated first value and the power budget.

In Example 20, the subject matter of Example(s) 19 may include the oneor more processor configured to reallocate power to the one or moreremaining circuits based on the updated second power value.

In Example 21, the subject matter of Example(s) 4-20 may include the oneor more processor configured to determine a cellular modem powerenvelope.

In Example 22, the subject matter of Example(s) 21 may include the oneor more processor configured to select cellular modem power consumptionparameters from one or more cellular modem internal state variables.

In Example 23, the subject matter of Example(s) 22 may include whereinthe one or more cellular modem internal state variables is at least oneof a RAT, RRC state, number of downlink and/or uplink componentcarriers, or a transmit power level.

In Example 24, the subject matter of Example(s) 21-23 may include theone or more processor configured to add parameters to cover cellularmodem power variations due to secondary parameters.

In Example 25, the subject matter of Example(s) 24 may include whereinone or more of the secondary parameters is a downlink throughout, anuplink throughput, an impedance in antenna mismatch, or one or morethermal parameters.

In Example 26, the subject matter of Example(s) 4-25 may include the oneor more processor configured to identify one or more trigger events inorder to determine the activity status.

In Example 27, the subject matter of Example(s) 26 may include whereinthe one or more trigger events is at least one of a measurement for cellre-selection in RRC idle mode, a tracking area update (TAU), or atransmit power control during active connection.

In Example 28, the subject matter of Example(s) 4-27 may include the oneor more processor configured to receive a modem throttling state inorder to determine the activity status.

In Example 29, the subject matter of Example(s) 28 may include the oneor more processor configured to classify the throttling state as one ofa plurality of levels.

In Example 30, the subject matter of Example(s) 29 may include whereinthe plurality of classes comprise a zero throttling level, a firstthrottling activity level, a second throttling activity level, and athird throttling level.

In Example 31, the subject matter of Example(s) 28-30 may include theone or more processor configured to determine the activity status of thecellular modem based on the modem throttling state.

In Example 32, the subject matter of Example(s) 1-31 may include the oneor more processor configured to determine an amount of time that thefirst circuit will remain in the activity status.

In Example 33, the subject matter of Example(s) 1-32 may include whereinone of the one or more remaining circuits of the plurality of circuitsis an application processor.

In Example 34, the subject matter of Example(s) 1-33 may include the oneor more processor configured to retrieve the first power value and/orthe updated first power value from a look up table (LuT) stored in amemory.

In Example 35, the subject matter of Example(s) 34 may include the oneor more processor configured to update the LuT as a result of a receivedsoftware update.

In Example 36, the subject matter of Example(s) 1-35 may include the oneor more processors configured to use machine learning to determine thefirst power value.

In Example 37, the subject matter of Example(s) 36 may include whereinthe machine learning uses cellular modem internal state variables todetermine the first power value.

In Example 38, the subject matter of Example(s) 22-37 may includewherein the cellular internal state variables includes one or more of aconnected Radio Access Technology (RAT); Radio Resource Control (RRC)state; number of component carriers (CCs); transmit (Tx) power levels;Application Processor or Packet Data Convergence Protocol (PDCP)indications for uplink data to be transmitted along with its buffersize; indications at Radio Link Control (RLC) or Media Access Control(MAC) level including scheduling requests, or buffer status reports; anumber of downlink and/or uplink CCs; dynamic activation/de-activationof the CCs by a network; a Modulation Coding Scheme (MCS); frequencyband information; or connected discontinuous reception cycle (C-DRX)state entry and/or exit indications from the communication device.

In Example 39, a method for allocating power among a plurality ofcircuits in a communication device, the method including determining apower budget for allocating to the plurality of circuits from a powersupply information; receiving an activity status from a first circuit ofthe plurality of circuits; determining a first power value based on theactivity status; deriving a second power value based on the first powervalue and the power budget; and allocating power to one or moreremaining circuits of the plurality of circuits based on the secondpower value.

In Example 40, the subject matter of Example(s) 39 may include obtainingthe power supply information from a battery of the communication device.

In Example 41, the subject matter of Example(s) 39-40 may include,wherein the power supply information comprises a state of charge of abattery of the communication device.

In Example 42, the subject matter of Example(s) 39-41 may includewherein the first circuit is a cellular modem of the communicationdevice.

In Example 43, the subject matter of Example(s) 42 may include whereinthe cellular modem is configured to operate according on one or moreradio access technologies (RATs).

In Example 44, the subject matter of Example(s) 43 may include whereinat least one of the RATs is configured to operate according to a RadioResource Control (RRC) protocol.

In Example 45, the subject matter of Example(s) 44 may includedetermining the activity status based on the cellular modem's RRC state.

In Example 46, the subject matter of Example(s) 45 may includedetermining whether the RRC state is idle mode or in connected mode.

In Example 47, the subject matter of Example(s) 46 may includedetermining the first power value based on the determination of the RRCstate being in idle mode or connected mode.

In Example 48, the subject matter of Example(s) 43-47 may includedetermining a number of carriers being used by the cellular modem.

In Example 49, the subject matter of Example(s) 48 may includedetermining the first power value based on the number of carriers.

In Example 50, the subject matter of Example(s) 43-49 may includedetermining radio channel conditions of the communication device.

In Example 51, the subject matter of Example(s) 50 may includedetermining the location based on a received signal from a base station.

In Example 52, the subject matter of Example(s) 50-51 may includewherein the location is a cell center or a cell edge of a cell on whichthe communication device is camped on.

In Example 53, the subject matter of Example(s) 42-52 may includedetermining the first power value based on a transmit level of thecellular modem.

In Example 54, the subject matter of Example(s) 39-53 may includesubtracting the first power value from the power budget in order toderive the second power value.

In Example 55, the subject matter of Example(s) 39-54 may includereceiving an updated activity status from the first circuit.

In Example 56, the subject matter of Example(s) 55 may includedetermining an updated first power value based on the updated activitystatus.

In Example 57, the subject matter of Example(s) 56 may include derivingan updated second power value based on the updated first value and thepower budget.

In Example 58, the subject matter of Example(s) 57 may includereallocating power to the one or more remaining circuits based on theupdated second power value.

In Example 59, the subject matter of Example(s) 42-58 may includedetermining a cellular modem power envelope.

In Example 60, the subject matter of Example(s) 59 may include selectingcellular modem power consumption parameters from one or more cellularmodem internal state variables.

In Example 61, the subject matter of Example(s) 60 may include whereinthe one or more cellular modem internal state variables is at least oneof a RAT, RRC state, number of downlink component carriers, or atransmit power level.

In Example 62, the subject matter of Example(s) 59-61 may include addingparameters to cover cellular modem power variations due to secondaryparameters.

In Example 63, the subject matter of Example(s) 62 may include whereinone or more of the secondary parameters is a downlink throughout, anuplink throughput, an impedance in antenna mismatch, or one or morethermal parameters.

In Example 64, the subject matter of Example(s) 42-63 may includeidentifying one or more trigger events in order to determine theactivity status.

In Example 65, the subject matter of Example(s) 64 may include whereinthe one or more trigger events is at least one of a measurement for cellre-selection in RRC idle mode, a tracking area update (TAU), or atransmit power control during active connection.

In Example 66, the subject matter of Example(s) 42-65 may includereceiving a modem throttling state in order to determine the activitystatus.

In Example 67, the subject matter of Example(s) 66 may includeclassifying the throttling state as one of a plurality of levels.

In Example 68, the subject matter of Example(s) 67 may include whereinthe plurality of classes comprise a zero throttling level, a firstthrottling activity level, a second throttling activity level, and athird throttling level.

In Example 69, the subject matter of Example(s) 66-68 may includedetermining the activity status of the cellular modem based on the modemthrottling state.

In Example 70, the subject matter of Example(s) 39-69 may include apredetermined amount of time that the first circuit will remain in theactivity status.

In Example 71, the subject matter of Example(s) 39-70 may includewherein one of the one or more remaining circuits of the plurality ofcircuits is an application processor.

In Example 72, the subject matter of Example(s) 39-71 may includeretrieving the first power value and/or the updated first power valuefrom a look up table (LuT).

In Example 73, the subject matter of Example(s) 39-72 may includeupdating the LuT as a result of a received software update for thecommunication device.

In Example 74, the subject matter of Example(s) 39-73 may include usingmachine learning to determine the first power value.

In Example 75, the subject matter of Example(s) 74 may include whereinthe machine learning uses cellular modem internal state variables todetermine the first power value.

In Example 76, the subject matter of Example(s) 75 may include, whereinthe cellular internal state variables includes one or more of aconnected Radio Access Technology (RAT); Radio Resource Control (RRC)state; number of component carriers (CCs); transmit (Tx) power levels;Application Processor or Packet Data Convergence Protocol (PDCP)indications for uplink data to be transmitted along with its buffersize; indications at Radio Link Control (RLC) or Media Access Control(MAC) level including scheduling requests, or buffer status reports; anumber of downlink and/or uplink CCs; dynamic activation/de-activationof the CCs by a network; a Modulation Coding Scheme (MCS); frequencyband information; or connected discontinuous reception cycle (C-DRX)state entry and/or exit indications from the communication device.

In Example 77, a method for configuring a plurality of processing blockson a chip specific to a battery providing power to the chip, the methodincluding deriving a function of a remaining data processing capacitydependent on battery current; selecting a range of battery current fromthe function delivering a desired data processing capacity; andconfiguring one or more of the plurality of processing blocks of theplurality of processing blocks based the selected range.

In Example 78, the subject matter of Example(s) 77 may includedetermining a local maximum of the function.

In Example 79, the subject matter of Example(s) 78 may include selectingthe range based on the local maximum.

In Example 80, the subject matter of Example(s) 77-79 may includewherein the range depends on a processing granularity of the pluralityof processing blocks.

In Example 81, the subject matter of Example(s) 77-80 may includewherein deriving the function comprises testing the battery at aplurality of battery operating loads to obtain the function.

In Example 82, the subject matter of Example(s) 77-81 may includestoring the function. This may include storing the function or valuesassociated with the function in a Look Up table (LUT).

In Example 83, the subject matter of Example(s) 77-82 may includemonitoring a battery information as the battery discharges.

In Example 84, the subject matter of Example(s) 83 may include, whereinthe battery information comprises at least one of a battery current or abattery state of charge.

In Example 85, the subject matter of Example(s) 83-84 may includemonitoring the plurality of processing blocks at one or more batterystate of charges.

In Example 86, the subject matter of Example(s) 83-85 may includefurther comprising monitoring the plurality of processing blocks at oneor more battery currents.

In Example 87, the subject matter of Example(s) 83-86 may includereconfiguring the one or more processing blocks of the plurality ofprocessing blocks based on a battery state of charge.

In Example 88, the subject matter of Example(s) 83-87 may includereconfiguring the one or more processing blocks of the plurality ofprocessing blocks based on a battery current.

In Example 89, the subject matter of Example(s) 77-88 may includedetermining a base operational current for maintaining one or moreprocessing blocks of the plurality of processing blocks powered on.

In Example 90, the subject matter of Example(s) 77-89 may includedetermining a minimum operational current for processing a selected dataat one or more processing blocks of the plurality of processing blocks.

In Example 91, the subject matter of Example(s) 90 may include whereinthe selected data includes data received by wireless communications.

In Example 92, the subject matter of Example(s) 91 may include whereinthe data is received according to one or more wireless protocols.

In Example 93, the subject matter of Example(s) 77-92 may includewherein the selected data includes application data for one or moreapplications.

In Example 94, the subject matter of Example(s) 77-93 may includeswitching at least one of the plurality of processing blocks on or offbased on the configuration.

In Example 95, a communication device with a battery dischargecontroller for controlling a plurality of processing blocks on a chipspecific to a battery providing power to the chip, the battery dischargecontroller configured to derive a function of a remaining dataprocessing capacity dependent on battery current; select a range ofbattery current from the function delivering a desired data processingcapacity; and configure one or more of a plurality of processing blocksof the plurality of processing blocks based the selected range.

In Example 96, the subject matter of Example(s) 95 may include thebattery discharge controller configured to determine a local maximum ofthe function.

In Example 97, the subject matter of Example(s) 96 may include thebattery discharge controller configured to select the range based on thelocal maximum.

In Example 98, the subject matter of Example(s) 95-97 may includewherein the range depends on a processing granularity of the pluralityof processing blocks.

In Example 99, the subject matter of Example(s) 95-98 may includewherein deriving the function comprises testing the battery at aplurality of battery operating loads to obtain the function.

In Example 100, the subject matter of Example(s) 95-99 may include thebattery discharge controller operatively coupled to a memory, whereinthe memory is configured to store the function in a Look Up table (LUT).

In Example 101, the subject matter of Example(s) 95-100 may include thebattery discharge controller configured to monitor a battery informationas the battery discharges.

In Example 102, the subject matter of Example(s) 101 may include whereinthe battery information comprises at least one of a battery current or abattery state of charge.

In Example 103, the subject matter of Example(s) 101-102 may include thebattery discharge controller configured to monitor the plurality ofprocessing blocks at one or more battery state of charges.

In Example 104, the subject matter of Example(s) 101-103 may include thebattery discharge controller configured to monitor the plurality ofprocessing blocks at one or more battery currents.

In Example 105, the subject matter of Example(s) 101-104 may include thebattery discharge controller configured to reconfigure the one or moreprocessing blocks of the plurality of processing blocks based on abattery state of charge.

In Example 106, the subject matter of Example(s) 101-105 may include thebattery discharge controller configured to reconfigure the one or moreprocessing blocks of the plurality of processing blocks based on abattery current.

In Example 107, the subject matter of Example(s) 95-106 may include thebattery discharge controller configured to determine a base operationalcurrent for maintaining one or more processing blocks of the pluralityof processing blocks powered on.

In Example 108, the subject matter of Example(s) 95-107 may include thebattery discharge controller configured to determine a minimumoperational current for processing a selected data at one or moreprocessing blocks of the plurality of processing blocks.

In Example 109, the subject matter of Example(s) 108 may include whereinthe selected data includes data received by wireless communications.

In Example 110, the subject matter of Example(s) 109 may include whereinthe data is received according to one or more wireless protocols.

In Example 111, the subject matter of Example(s) 95-110 may includewherein the selected data includes application data for one or moreapplications.

In Example 112, the subject matter of Example(s) 95-111 may include thebattery discharge controller configured to switch at least one of theplurality of processing blocks on or off based on the configuration.

In Example 113, one or more non-transitory computer readable mediaincluding program instructions, which when executed by one or moreprocessors perform a method or realize a device as claimed in anypreceding claim.

In some aspects, the power budget determined from the power supplyinformation may be allocated according to different priorities to theplurality of circuits (e.g. LTE cellular modem or other RAT cellularmodem; Application Processor (i.e. SoC); WiFi, Near Field Communication(NFC) or Bluetooth transceiver(s); display; speakers, etc.). Forexample, a first power value associated with an LTE cellular modem maybe accorded a higher priority than a second power value associated withan Application Processor, and accordingly, the second power value may bedetermined from the power budget after the first power value isdetermined for allocation to the LTE cellular modem. Similarly, thismethod of prioritization of resources from the power budget may beapplied to other UE components, e.g. first prioritize assigning therequired power to the speaker(s) of the UE, and then adjust the power tothe UE display if playing audio files, for example. In this manner, UEcomponents with lower priority are assigned power from the power budgetafter determining the power to assign to higher priority components,depending on the use case.

While the above descriptions and connected figures may depict electronicdevice components as separate elements, skilled persons will appreciatethe various possibilities to combine or integrate discrete elements intoa single element. Such may include combining two or more circuits forform a single circuit, mounting two or more circuits onto a common chipor chassis to form an integrated element, executing discrete softwarecomponents on a common processor core, etc. Conversely, skilled personswill recognize the possibility to separate a single element into two ormore discrete elements, such as splitting a single circuit into two ormore separate circuits, separating a chip or chassis into discreteelements originally provided thereon, separating a software componentinto two or more sections and executing each on a separate processorcore, etc.

It is appreciated that implementations of methods detailed herein areexemplary in nature, and are thus understood as capable of beingimplemented in a corresponding device. Likewise, it is appreciated thatimplementations of devices detailed herein are understood as capable ofbeing implemented as a corresponding method. It is thus understood thata device corresponding to a method detailed herein may include one ormore components configured to perform each aspect of the related method.

All acronyms defined in the above description additionally hold in allclaims included herein.

While the invention has been particularly shown and described withreference to specific aspects, it should be understood by those skilledin the art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the invention as definedby the appended claims. The scope of the invention is thus indicated bythe appended claims and all changes, which come within the meaning andrange of equivalency of the claims, are therefore intended to beembraced.

What is claimed is:
 1. A communication device for wirelesscommunications, the communication device comprising at least oneprocessor configured to: determine a power budget for allocating to aplurality of circuits based on a power supply information; receive anactivity status from a first circuit of the plurality of circuits;determine a first power value based on the activity status; derive asecond power value based on the first power value and the power budget;and allocate power based on the second power value to a second circuitof the plurality of circuits.
 2. The communication device of claim 1,the at least one processor configured to obtain the power supplyinformation from a battery of the communication device.
 3. Thecommunication device of claim 1, wherein the first circuit is a cellularmodem.
 4. The communication device of claim 3, wherein the cellularmodem is configured to operate according on one or more radio accesstechnologies (RATs).
 5. The communication device of claim 4, the atleast one processor configured to determine the activity status based onthe cellular modem's RAT connected state.
 6. The communication device ofclaim 3, the at least one processor configured to determine a number ofcarriers used by the cellular modem.
 7. The communication device ofclaim 6, the at least one processor configured to determine the firstpower value based on the number of carriers.
 8. The communication deviceof claim 1, the at least one processor configured to observe radiochannel conditions and use the observed radio channel conditions todetermine the first power value.
 9. The communication device of claim 1,the at least one processor configured to subtract the first power valuefrom the power budget in order to derive the second power value.
 10. Thecommunication device of claim 1, the at least one processor configuredto receive an updated activity status from the first circuit.
 11. Thecommunication device of claim 10, the at least one processor configuredto determine an updated first power value based on the updated activitystatus.
 12. The communication device of claim 11, the at least oneprocessor configured to derive an updated second power value based onthe updated first value and the power budget.
 13. The communicationdevice of claim 12, the at least one processor configured to reallocatepower to the one or more remaining circuits based on the updated secondpower value.
 14. The communication device of claim 1, the at least oneprocessor configured to select cellular modem power consumptionparameters for determining the first power value from one or morecellular modem internal state variables including one or more of: aconnected Radio Access Technology (RAT); Radio Resource Control (RRC)state; number of component carriers (CCs); transmit (Tx) power levels;Application Processor or Packet Data Convergence Protocol (PDCP)indications for uplink data to be transmitted along with its buffersize; indications at Radio Link Control (RLC) or Media Access Control(MAC) level including scheduling requests or buffer status reports; anumber of downlink and/or uplink CCs; dynamic activation/de-activationof the CCs by a network; a Modulation Coding Scheme (MCS); frequencyband information; or connected discontinuous reception cycle (C-DRX)state entry or exit indications from the communication device.
 15. Thecommunication device of claim 1, the at least one processor configuredto receive a throttling state from the first circuit.
 16. Thecommunication device of claim 15, the at least one processor configuredto classify the throttling state as one of a plurality of levels, anduse the classification to determine the first power value.
 17. A methodfor allocating power among a plurality of circuits in a communicationdevice, the method comprising: determining a power budget for allocatingto the plurality of circuits from a power supply information; receivingan activity status from a first circuit of the plurality of circuits;determining a first power value based on the activity status; deriving asecond power value based on the first power value and the power budget;and allocating power to one or more remaining circuits of the pluralityof circuits based on the second power value.
 18. The method of claim 17,further comprising obtaining the power supply information from a batteryof the communication device.
 19. One or more non-transitorycomputer-readable media storing instructions thereon that, when executedby at least one processor of a communication device, direct the at leastone processor to perform a method comprising: determining a power budgetfor allocating to a plurality of circuits from a power supplyinformation; receiving an activity status from a first circuit of theplurality of circuits; determining a first power value based on theactivity status; deriving a second power value based on the first powervalue and the power budget; and allocating power to one or moreremaining circuits of the plurality of circuits based on the secondpower value.
 20. The one or more non-transitory computer-readable mediaof claim 19, further comprising obtaining the power supply informationfrom a battery of the communication device.
 21. A communication devicecomprising a battery discharge controller for controlling a plurality ofprocessing blocks, the battery discharge controller configured to:derive a function of a remaining data processing capacity dependent onbattery current; select a range of battery current from the functiondelivering a desired data processing capacity; and configure one or moreof a plurality of processing blocks of the plurality of processingblocks based the selected range.
 22. The communication device of claim21, the battery discharge controller further configured to determine alocal maximum of the function.
 23. The communication device of claim 22,the battery discharge controller further configured to select the rangebased on the local maximum.
 24. The communication device of claim 21,wherein the range depends on a processing granularity of the pluralityof processing blocks.
 25. The communication device of claim 21, thebattery discharge controller operatively coupled to a memory configuredto store the function.